Sales Calls and Pipeline Desk Official

When a call is logged it reads the transcript from the call notes tool, writes the summary, the objections and the next steps with dates, drafts the CRM note and the follow-up task (both behind approval) and drafts the follow-up email for a person to send.

1. 01Call "{{call}}" on deal "{{deal}}" with {{contact}} on {{when}} via {{phone_tool}}, recording {{recording}}. Read the transcript from the call notes tool. Write "Summary:" three lines, "Objections:" one per line in the customer's words, "Next steps:" one per line with a date and an owner, per the playbook. Output: The summary, objections and next steps, plain text.
2. 02Write the Objections and Next Steps columns on the call. Set the deal's Next Step to the first next step and Last Activity to the call's date. Set the contact's Last Touch. Write the call note into the CRM on the deal and create the follow-up task for the deal owner (both wait for approval). Set CRM Note to Drafted and Status to Summarised. Draft the follow-up email under 120 words; never send it. Plain text. Output: The CRM note as written, the task, and the follow-up email draft, plain text.

Every weekday morning it reads the open deals, updates how long each has been quiet and its risk, and for anything quiet for 7 days, past its close date or without a next step it drafts a nudge to the owner and a touch to the customer. A person sends both.

1. 01Read every deal whose Stage is not Won or Lost. From the CRM find the last activity on each. Update Last Activity, Days Quiet and Risk (On track, Watch at 4 days, At risk at {{quiet_days}} days or more (default 7), Slipped when the close date has passed). Output: Each open deal with its days quiet and risk, plain text lines.
2. 02For each deal that is At risk, Slipped or has an empty Next Step, create a Nudges row (Nudge, Deal, Kind, Owner, Created today, Status Drafted) with the Draft: "To the owner:" the nudge, then "To the customer:" the two-sentence touch. Write the same into the deal's Nudge Draft. Skip a deal that already has a Drafted nudge. Email each owner their nudge with Turtle Notify. Plain text. Output: The nudges created and the emails drafted, plain text.

Every weekday morning it reads today's calendar, and for each meeting with an outside attendee it enriches the contact and writes a one-page brief: the company, the person's role and recent changes, the last conversation, the open deal and its next step, two questions to ask. Also runs from the Brief me button on a contact.

1. 01If a contact was given ({{contact}}, {{title}} at {{company}}, {{email}}, deal "{{deal}}"): prepare a brief for that contact. If not: read the calendar for {{day}} (default today) and list every meeting with an attendee outside the company; match each attendee to a Contacts row by email, creating the row when there is none. For each contact, enrich the person and the company with the enrichment tool and read the last conversation from Calls and the CRM. Output: The contacts to brief with what the enrichment found, plain text.
2. 02For each contact write the Pre-call Brief per the playbook: company in two lines, role and any recent change, the last conversation and what was promised, the open deal with its stage and next step, two questions to ask. Fill in Title, Company and Phone where empty. Set Enriched (Enriched or Not found) and Brief to Ready. Plain text, under 200 words per brief. Output: The briefs written, plain text.

When a deal changes stage it finds every contact on that deal in a sequence, pauses the sequence when the deal reaches Meeting or is closed either way, and flags the contact for the owner when the deal is Lost. Pausing waits for a person.

1. 01Deal "{{deal}}" ({{account}}, CRM id {{crm_id}}) moved to stage {{stage}}. Find the contacts on this deal and every Sequence Runs row for them with Status Active. Read each sequence's state in the sequencer. Output: The sequence runs affected with their current step, plain text.
2. 02If the stage is Meeting, Won or Lost: pause each active sequence in the sequencer and set the row's Status to Paused. If the stage is Lost: set Status to Flagged instead and write one line for the owner to remove the contact. Write a Sync Note on each row: what was done and why, per the playbook. If the stage is anything else, write one line saying nothing changed. Plain text. Output: The rows updated and the sync notes, plain text.

Every Friday afternoon it counts the pipeline by stage, what was created, won, lost and slipped this week, lists the slipped deals with the reason, writes three decisions for Monday with owners, creates the Pipeline Reviews row and emails the sales manager.

1. 01Week ending {{week}} (default this Friday). Count the open pipeline by Stage (sum of Amount), the deals created this week, won, lost, and slipped (close date passed or moved out). For each slipped deal find the reason in its calls, nudges and CRM notes. Output: The numbers and the slipped deals with reasons, plain text lines.
2. 02Write the review per the playbook: "Pipeline by stage:" one line per stage, "This week:" created, won, lost, slipped, "Slipped:" one line per deal with the reason, "Decisions for Monday:" three items each with an owner. Create the Pipeline Reviews row (Week, the numbers, Decisions, Status Drafted). Email it to the sales manager with Turtle Notify. Under 250 words, plain text. Output: The review as sent, plain text.