Define today before asking for today's work
Tell your AI which time zone to use and who the list is for. A due timestamp near midnight can belong to different calendar days in different places. Give the connection an explicit start and end for the workday you want to inspect.
Relay's task reference documents filters for open status and due timestamps. It treats those timestamps as stored instants. Have your AI use the current reference to translate your chosen local day into the request it makes.
Read enough of the list to describe it
Use task and contact read permissions for the first version. Ask the AI to follow the documented paging behavior and identify a partial result. A page of tasks is useful, but it doesn't establish that the account has no other open work.
Keep overdue work in view. Also separate tasks with no due date so you can decide what to do with them. The AI should preserve the task's status and contact association when it prepares your list.
Sort by the commitments you made
Avoid ranking people by guesses about their finances or urgency. Your own notes and agreed commitments provide a concrete basis for the list. If the available history doesn't explain why a task exists, open the record before contacting the client.
- Review overdue tasks and any work you promised for today.
- Group tasks by contact so you can see related work before reaching out.
- Mark missing details, such as an unclear promise or an absent due date.
- Choose the work you will do next and approve any proposed task changes.
A prompt to adapt
Prepare my follow-up list from Relay.
Assignee: {{confirmed user or account scope}}
Local date and time zone: {{date and zone}}
My recorded priorities: {{priorities}}
Use the current task API reference to read open tasks in the chosen time window, plus overdue tasks and tasks without due dates where available. Follow pagination and state any incomplete coverage. Read the contact context needed to explain each task.
Group related tasks by contact. Show due dates in my time zone and preserve the stored status. Flag unclear instructions or missing details. Suggest an order based on my recorded commitments.
Return the list for review. Leave task changes and client messages unsaved until I approve them.Keep the history boundary visible
Relay's notes and activity endpoints describe Relay-local records. A contact record doesn't prove that your AI has read every call, email, or conversation associated with that person. Only claim the history the connection returned.
In a fictional example, a contact has an open task to send a listing and no recent local note. Ask to check the available record. Don't turn that absence into 'the client hasn't heard from us.' A conversation may have happened elsewhere.
Close the loop after you do the work
After the call or delivery, record the outcome and decide whether the task is complete. Ask the AI to propose the update if you want help. Completing a task in Relay should reflect work you performed or verified.
If the list feels too long, narrow the next request to a confirmed assignee or a specific group of records. Keep the first version read-only until the daily list is accurate enough to use. Relay's directory rate is $29/mo; account features and your AI plan still need their own checks.
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.