# Follow through on sales calls You have access to a call-recording tool, a CRM, an email account, an issue tracker, and a messaging tool. Run this for **[the sales call that just ended]**. ## 0. Set up (skip if you're already connected) If you don't already have live tool access for this, connect it first. This prompt is only as real as the tools behind it: 1. Get a Tulina account: book a demo at https://tulina.ai/book. 2. Add Tulina's MCP server to your assistant: https://mcp.tulina.ai/mcp 3. In Tulina, connect your own API keys for the tools this prompt uses: your call-recording tool, your CRM, your email account, your issue tracker, and your team's messaging tool. Once connected, your assistant has real tool access and the rest of this prompt runs as written. ## 0b. Already on Tulina? Three things around the run An account and the MCP server are not the whole setup. Two of these come before the run below and one after it, and together they turn this from a one-off answer into a process your workspace keeps: 1. **Activate this process's connectors first.** Call `oto_connector(op="list")`, match it against the tools named in step 3 above, and `oto_connector(op="select", name="...")` every one that isn't active yet. Selecting a connector does not mount its tools in the conversation you're already in — reach them through `oto_call` for this run, or open a fresh conversation once they're all on. 2. **Attach the work to an existing project.** `oto_project(op="list")` shows your active org's projects: pick the one this work belongs to rather than opening another, and keep its id. The project is where this process, the tables it writes to and the connectors it uses hang together. 3. **When the run is done, save it as a process — with its graph.** Write the body with `oto_procedure(op="set", ...)`, then attach it with `oto_project(op="link", project_id=..., target_type="procedure", target_ref="")`. The body has to carry a drawing: read `oto_guide(op="read", slug="procedure-flowchart")` and follow it exactly — ONE untagged fenced block in that grammar, opening with the trigger and a quoted example of what you'd type to start a run. Tulina parses that drawing back into the graph it renders as the process's default view, which is what makes it come out in the same style as every other process in the app; a drawing the grammar can't read falls back to raw characters instead. Saving a process needs org-admin rights — without them, hand the finished body to someone who has them. ## 1. Pull the deal and its history Find the call's notes: title, date, participants and summary. Then find the deal the call belongs to. Match on the external attendees' email domain as well as on their names, since the person on the call is often not the contact the deal was opened under. If two open deals share the company, take the one whose contacts were on the call, and say which you chose. Read the deal record: stage, amount, close date, owner, the next step as it is currently written, and the notes already attached. Read the most recent email thread with the same people. If no deal matches, stop and report the call as unmatched. Do not create a deal from a call. ## 2. Extract pains, objections and next steps From the call notes, keep only what moves the deal: - What they said they need, in their own words. - What they pushed back on: price, timing, a missing capability, a competitor, an internal blocker. - Who was on the call and what each person cared about. Anyone new to the deal is a stakeholder to add. - What each side agreed to do, and by when. - Anything they asked the product to do that it does not do today. Quote rather than paraphrase. A summary in internal vocabulary reads fine in the CRM and is useless in the follow-up. ## 3. Judge the deal against your playbook Read what came out of step 2 against **[your qualification criteria]**: what has to be known before a deal earns each stage. - Name what is still unknown for the stage the deal is in. - Decide whether the deal is at risk, and say why in one line: a new objection, a stakeholder who has gone quiet, a close date that no longer matches what they said, a next step with no date. A deal is not at risk because the call was short. It is at risk when something said on the call contradicts what the record says. ## 4. Test any offer against your pricing rules Read the same notes against **[your pricing rules: what a rep may and may not offer, the discount bands, the floor prices, the terms that need an approval]**. Flag anything said on the call that is outside them: a discount hinted at, a term promised, a delivery date, a pilot for free. Quote it, and name the rule it crosses. If no pricing rules are written down, flag nothing on this count and say that none were found. ## 5. Update the deal, log the next step Write back to the deal, changing only what the call changed: - The next step, with its date and its owner. - The close date, if what they said moves it. Report what it was before. - New stakeholders, as contacts on the deal. - One note on the record: needs, objections, commitments and what is still unknown, each with the quote it came from. Do not move the stage. Report whether the call earned the next one under your criteria, and leave the move to the deal's owner. ## 6. File product asks with their quotes For each thing they asked the product to do, search the tracker for an existing issue on the substance of the request, not on its wording. If one exists, add a comment carrying the quote, the account and the deal amount. If none does, create an issue on the owning team's board with the same three things. A request with a deal attached is not the same as a request. The amount is the reason it goes on the issue. ## 7. Draft the follow-up, flag the risk Draft the follow-up as a reply on the existing thread, to the people who were on the call: what they said they need, in their words; what you agreed to do and by when; what you need from them and by when. No pitch. **Create it as a draft. Never send it.** If step 3 found the deal at risk, or step 4 found something outside the pricing rules, post one message in the team channel for the owner's manager: the deal, the one-line reason, and the quote behind it. If neither found anything, post nothing. ## Output Report: the call and the deal it matched, the fields changed on the deal with their previous values, stakeholders added, product asks filed or commented on, whether the follow-up draft was created, and whether a risk was flagged and why.