About SendGrid
SendGrid, a Twilio product, provides email delivery infrastructure for transactional and marketing messages. The Crassula connector is relevant to account notifications, verification emails and other configured customer communications. Email delivery can support a verification workflow, but SendGrid does not itself identify a customer or authorise a banking payment. Those decisions remain within the configured application and security processes.
Organising customer email journeys
Transactional email connects a product event with a message the customer needs to receive. Typical journeys include account updates, verification requests and service notifications. The implementation should make clear which event sends a message, which recipient is selected and how the business handles an unsuccessful delivery.
- Define message purpose, recipient and product trigger.
- Prepare branded templates and appropriate language versions.
- Plan delivery monitoring and customer-support follow-up.
The value is consistency across the customer journey. A message should explain the relevant event and any next step clearly. Product teams can coordinate email content with the interface the customer sees, while operations teams know how to investigate a missing or unexpected notification and maintain the surrounding communication process.
Working with the connector
Crassula provides the software layer for organising customer journeys and operational processes around the connected service. A team can bring the functions included in its implementation into a branded product, while retaining a common place to review customer information, service requests and the resulting operational records. The provider continues to deliver its part of the service under the relevant agreement.
A useful starting point is to map the customer journey from the initial request to its final outcome. Define which information is submitted, what response is expected, which status is shown to the customer and how an operator handles an exception. This makes it easier to design a clear experience and to identify where automated processing or human review is appropriate.
Planning your implementation
Agree the required functions with Crassula and the provider, then test the complete journey in the available test environment. Include successful requests, incomplete data, unsuccessful responses and recovery after an interruption. Establish responsibility for customer support, operational follow-up and changes to the provider service. The connector can then become part of a documented product workflow, with clear expectations for customers and the team operating it.
Provider and connector overview
The gallery gives a provider-specific visual overview. Official imagery is included where available, alongside a simplified explanatory diagram of the connector’s role in a Crassula product.
