A call ends and its record in your CRM gets the note, with each follow-up waiting as a task. You do not copy a summary or retype the next steps.
This is written and not switched on. All five adapters and the whole note-and-tasks pipeline exist, and the send works when it is called. What is missing is the front of it: no CRM OAuth application is configured on our side, so the connect card shows a setup screen rather than a Connect button and nobody can authorize one today. The Send menu does not list a CRM either, and nothing runs on its own when a call ends.
We are keeping this page because the shape is settled and the work is nearly all done. If a CRM is what would make Sayli worth it for your team, say so at support@sayli.ai. That is what decides the order.
What Sayli writes
Two things land when a send runs.
The note is the brief: what was said, what was decided, what comes next. Every to-do becomes its own task, so nothing lives only in your head.
Matched by email
Sayli matches the right record by attendee email. The people on the call are the people on the record. When their email is on a contact in your CRM, that is where the note and tasks go.
If an attendee email does not map to a record, Sayli leaves it alone rather than writing to the wrong place.
Supported CRMs
Five are built, and none can be connected yet, for the reason at the top of this page. Each is designed to connect once per organization with OAuth.
- Attio
- HubSpot
- Salesforce
- Pipedrive
- Zoho
When it is switched on
The connection will be made once per workspace, through your CRM's own sign-in, and a connected CRM will appear in the brief's Send it on menu. Every send previews which attendees matched before anything is written, and sending the same call again returns the earlier result instead of logging it twice.