Communication
Scope business messaging around a clear customer workflow.
Explore data & scopeCommunication · Email & SMSCustom integration — assessment required
Design notifications with a clear sender and outcome.
Existing configured Brevo email workflows can send specific operational emails and record provider responses. New email workflows and SMS integrations require assessment. This combined category is not an assurance of a general messaging connector.
Email & SMSAuthorised source / destination
01
Configured operational emailSalesTOS → Brevo
02
Provider responseBrevo → SalesTOS
03
New email templatesSalesTOS → provider
SalesTOSExisting scoped email workflows
Record ownership and direction are defined below. No universal two-way sync is implied.
The operational need
Why connect these systems?
Operational messages need an approved sender and recipient.
A provider accepting an email is different from confirmed delivery.
SMS fallback should not happen without an agreed workflow.
Direction, ownership, prerequisites
What data can be exchanged?
Each row is a separate scope decision. Supported workflows still require configuration; proposed records require assessment and implementation.
| Record or object | Direction | System of record | Purpose | Availability / prerequisites |
|---|---|---|---|---|
| Configured operational email | SalesTOS → Brevo | SalesTOS for message request | Existing scoped email workflows | Available only for configured supported workflows |
| Provider response | Brevo → SalesTOS | Brevo | Send result and provider reference | Existing communication logging; not proof of delivery |
| New email templates | SalesTOS → provider | Agreed workflow | Candidate notifications | Assessment and implementation required |
| SMS requests and outcomes | Proposed two directions | Provider for delivery outcome | Candidate text notifications | SMS connector requires assessment |
Connection design
How the connection works
The existing mail service calls Brevo’s transactional email interface using configured credentials. Additional templates, triggers and delivery-event processing must be reviewed. Generic SMS registry entries do not establish production delivery.
Illustrative working scenario
From system context to a useful next action.
A configured review-meeting workflow sends an email and stores the send outcome. An additional SMS reminder would need its own provider, recipient rules and implementation.
What happens to writeback?
Message acceptance does not approve a record, settle a payment or prove the recipient read it.
Before implementation
Setup requirements
- Email/SMS provider and sender ownership
- Required trigger and message examples
- Recipient rules and failure handling
- Authorised configuration through a secure setup process
Use an authorised setup process for credentials. The enquiry form does not request passwords or API secrets.
Operating the agreed scope
Reliability & access
Existing email logging records send success/failure and provider references. Delivery callbacks, SMS retries and automatic fallback must be assessed separately; they are not implied by an accepted API request.
A clearer scope starts here
Questions, answered.
Email & SMS integration
Does sent mean delivered?
No. Provider acceptance and recipient delivery are distinct events.
Which email provider is implemented?
Configured Brevo transactional email is used in existing scoped workflows.
Is SMS automatically available?
No. Provider-specific implementation and permissions require assessment.
Can failed email fall back to SMS?
That needs a separate agreed workflow; it is not a default capability.
What should we prepare for a Email & SMS discussion?
Email/SMS provider and sender ownership; Required trigger and message examples; Recipient rules and failure handling; Authorised configuration through a secure setup process. Share redacted examples through an agreed channel, never passwords or API secrets in the public form.
How is Email & SMS integration scope confirmed?
Review the objects and prerequisites on this page, then agree mapping, access, refresh timing and acceptance criteria. Message acceptance does not approve a record, settle a payment or prove the recipient read it.
No matching questions. Clear your search or discuss your requirements with us.
Explore the adjacent workflow
Related integrations
ERP & Accounting
ERPNext
AvailableConnect employee identity and attendance events.
Explore data & scopeReporting & Data
Excel & CSV
File import supportedStart with an approved template and a reviewable import.
Explore data & scopeYour systems. A defined scope.
Discuss This Integration Discuss Email & SMS with SalesTOS.
Bring your business workflow and current setup. We’ll use them to assess the right data scope.