Write down the promise before it gets lost
You finish a call and open another message. Later, you remember that you promised to send something. Start the workflow with that promise. Your notes need to say what the client asked for and what you agreed to do.
Keep the client's words separate from your interpretation. 'Send the two listings we discussed' is a task. 'They are ready to buy this week' needs evidence from the conversation. An AI can turn either phrase into a polished CRM note, so give it the right one.
Connect the permissions this task needs
Relay's public developer reference documents contact and task operations. An account admin creates an API key in Settings, under API Keys. For this workflow, reading contacts and tasks is the starting point. Saving a note or a task requires the matching write permission as well.
Relay scopes apply across the account, not to a short list of selected contacts. Keep your AI's work limited to the contact you name. Use the connection's credential settings for the key; don't include it in a call summary.
Match the person before changing the record
If two contacts share a phone number, stop and identify the right person. A shared detail is a reason to check. It doesn't prove that the records belong to the same client.
- Find the contact by a known email address or another identifier you have confirmed. Have the AI show the matched record.
- Read the current note context and open tasks available to the connection. Check for an existing task covering the same promise.
- Draft a factual note and one proposed next task. Include a due date only when you agreed on one or choose one yourself.
- Approve the exact note and task. After saving, retrieve them and check the contact association.
A prompt to adapt
Use Relay to prepare a follow-up for this contact.
Confirmed contact identifier: {{email or record ID}}
Approved call notes: {{notes}}
My chosen due date and time zone, if any: {{date and zone}}
Find the contact and show me the match. Read the available notes and open tasks. Then propose a factual call note and the next task, including its contact and due date. Flag an existing task that covers the same work.
Wait for my approval before writing. After an approved save, retrieve the resulting records so I can verify them. Keep any client message as an unsent draft.An example with a small but useful boundary
Fictional call note: 'Buyer asked for the two homes with a dedicated office. I said I'd send them Thursday.' The proposed task is to send those specific listings. The AI should ask you which Thursday and which time zone if your notes don't establish them.
The task still needs a status after you save it. Creating a reminder doesn't establish that you sent the listings. If you also ask for a client message, review that draft on its own before authorizing delivery.
Check the save when a response is unclear
If the connection loses a response, inspect Relay before repeating the write. Follow the current API reference for retry behavior; Relay documents replay protection for some local operations, while legacy writes have different behavior. Avoid assuming a failed response means nothing was saved.
Relay's directory rate is $29/mo. Your AI subscription is a separate cost. Start with one reviewed call so you can judge whether the saved note and task are useful in your own process.
Sources and review notes
Product information and starting prices checked October 17, 2026. These guides use documented product information and suggested workflows. We have not tested these connections for the directory. Relay's supplied directory rate is $29/mo. Provider plans, coverage, and permissions can change.