Operator
Replies written. Numbers updated. Proposals prepared. Operator brings your tools and context together, shows you the work, and learns from every correction you make.
10 operations todo
The annual option and the legal recap, ready in one reply.
Sarah asked two things, and both have answers in your files. The annual option comes from the approved pricing; the legal date comes from the meeting and Dan’s email.
Hi Sarah, Yes, paying annually takes 12% off the list price for your 40 seats. The joint legal review is Thursday at 15:00. Dan sent the security packet on Monday, so both teams have it ahead of the call. Shall I send over the annual quote and the calendar invite? Alex
Sarah Chen · 2 messages · Today 08:12
Hi Sarah, Sharing the updated per-seat pricing for the Q3 rollout: 40 seats across Product and Support, onboarding in two waves. Happy to walk through it live. Alex
Thanks for the breakdown. Is there a discount if we commit for the year upfront? And where did we land on the legal review? David mentioned a joint call but I never saw an invite. Sarah
The answer may be in an email, the numbers in a CRM, and the template in Drive. Operator gathers what it needs across your connected accounts, then prepares the work in the tools where it belongs.
Use several integrations in the same operation. Read a Zendesk ticket, check the account in HubSpot, find the answer in Notion, and prepare the reply. Or combine two CRMs in one report and share the result in Slack.
Gmail
Outlook
Zendesk
Intercom
Help Scout
Google Drive
Google Docs
Notion
Dropbox
Salesforce
HubSpot
Zoho
Airtable
Slack
Teams
Zoom
Google Calendar
Asana
Linear
ClickUp
Todoist
Zapier
Make
n8n
TrelloEmails, recordings, notes, client history, files, and web research can all contribute to the same piece of work.
Explore the integrationsWork with Operator as you would with a colleague. Change a sentence, fix a calculation, choose a better source, or explain how you want the result structured.
Our own learning model uses those corrections to teach future runs. It learns the pattern behind the change and carries it into the next similar task: your tone, your team’s rules, and the details you expect it to include.
The learning continues as you work. Your company DNA, approved examples, and fresh feedback help Operator get closer to the way your team does things.
Correct the work. Edit it directly or tell Prism what to change by voice or chat.
Carry the lesson forward. The next relevant operation starts with what you taught it.
Keep improving. Review the result, refine it, and build on the corrections that came before.
I prepared the follow-up from the meeting and the approved pricing.
Hi Sarah, Thank you for taking the time to speak with us about the Q3 rollout. Following our discussion, I wanted to share the annual option and an update on the legal review. The annual option includes a 12% discount for your 40 seats. The legal review is scheduled for Thursday at 15:00, and Dan has already sent the security packet. Please let me know if you have any questions or would like me to arrange the next steps. Alex
Ask for a proposal and Operator can find your presentation template, read the meeting, check the pricing sheet, and gather context from Slack, email, previous decks, and the web. Then it prepares the slides and the document you need.
The same approach works for a KPI spreadsheet, a sales playbook, or updates across several CRMs. Inspect the result, change a value, or accept individual edits before applying the work.
4 operations todo
A three-slide proposal and a one-page summary for the partners.
Julie needs something she can forward. The deck uses her words from the meeting, the agreed pilot from Slack, and the approved pricing. The one-pager carries the same offer for partners who prefer a document.
The title uses Julie’s wording. The proposal follows her meeting requirements.
Proposal summary for the partners
Paperwork after every client visit takes time away from the next customer. The team needs the conversation to stay with the account.
One coastal team, two claim types, three weeks. Start after the security review. Agree the success criteria with Julie before kickoff.
The approved annual option is attached to the proposal. Review the pilot with the partners on Tuesday, then confirm the rollout scope.
Your templates, approved pricing, and earlier work give the result its shape. The customer’s words give it context.
Read the reply. Open the deck. Check the changed cells. The work itself is ready for your decision.
Send the email, update the connected file, or write back to the right CRM from the same operation.
Turn the week’s meetings into a batch of personal follow-ups. Every recipient gets the right recap, promise, and next step, with progress visible as the work runs.
If one item needs attention, Operator keeps it separate. A bounced address can be checked against the account history. A draft with an unsupported reference is held, explained, and moved into its own operation for correction.
1 operations todo
One batch, with each promise and next step written for the person.
Each person gets their own recap and next action. I check every item as it runs and hold anything whose source does not match.
Hi {{first_name}}, Thanks for the time this week. Here is what we agreed: {{commitment_recap}} Next step on our side: {{next_step}}. I will have it with you by {{due_date}}. Alex
Nine sent. Piotr’s draft refers to a meeting that is not in his history. I held it so you can fix the source before it goes out.
Start by reviewing the work together. As Operator learns your corrections, give it recurring tasks with a clear scope: what starts the work, which tools it can use, and which actions still need your decision.
You choose the level of automation for each workflow. Routine work can run automatically; new situations and exceptions return to you with the context needed to decide. The activity history keeps the sources, changes, and result together.
Find the commitments, draft a personal email, add the activity to the client, and create the next task.
Read the conversation, find the approved answer, and check the customer’s account. Bring unusual requests back to the team.
Combine activity from multiple CRMs, update the KPI sheet, and prepare a short report for the team, using your reporting rules.
Turn an agreed deal into a project, carry over the promises, attach the brief, and let the delivery team know what happens next.
Start with a conversation. “Prism, prepare the proposal for Julie.” “Update the weekly sheet.” “Handle these after every review call.” Say what you want by voice, chat, or a phone call. Operator takes the work from there.
Talk to PrismGive Operator the work. Make it yours. Build on every correction.
Try the demoEvery surface feeds the others. Walk through the rest.
The annual option and the legal recap, ready in one reply.
Sarah asked two things, and both have answers in your files. The annual option comes from the approved pricing; the legal date comes from the meeting and Dan’s email.
Hi Sarah, Yes, paying annually takes 12% off the list price for your 40 seats. The joint legal review is Thursday at 15:00. Dan sent the security packet on Monday, so both teams have it ahead of the call. Shall I send over the annual quote and the calendar invite? Alex
Sarah Chen · 2 messages · Today 08:12
Hi Sarah, Sharing the updated per-seat pricing for the Q3 rollout: 40 seats across Product and Support, onboarding in two waves. Happy to walk through it live. Alex
Thanks for the breakdown. Is there a discount if we commit for the year upfront? And where did we land on the legal review? David mentioned a joint call but I never saw an invite. Sarah
Give procurement the multi-year number they asked for.
Marcus asked a buying question, and it has not been answered. I prepared the three-year option with a clear validity date, so procurement has a concrete next step.
Hi Marcus, For a three-year commitment to the full EU rollout, the approved option is 11% off the yearly number, fixed for the term. That brings the annual price to $106,800. I can hold these terms through Friday. Would a short call with procurement on Thursday help close the remaining questions? Alex
Marcus Henderson · Last reply Tuesday · Silent 2 days
Terms received, forwarding to procurement. One thing that came up internally: if we committed for the full EU rollout period rather than year by year, what does that do to the number? Marcus
One batch, with each promise and next step written for the person.
Each person gets their own recap and next action. I check every item as it runs and hold anything whose source does not match.
Hi {{first_name}}, Thanks for the time this week. Here is what we agreed: {{commitment_recap}} Next step on our side: {{next_step}}. I will have it with you by {{due_date}}. Alex
Nine sent. Piotr’s draft refers to a meeting that is not in his history. I held it so you can fix the source before it goes out.
Review the changed cells. The connected sheet follows when you apply.
The call count and DACH demos changed. DataDrive closed in the West, and Wisła moved into Negotiation in DACH. I recalculated the total from the regional rows. You can edit any highlighted value before applying.
| 1 | Region | Calls | Demos | Pipeline ($K) | Won ($K) |
|---|---|---|---|---|---|
| 2 | North | 12 | 310 | 42 | |
| 3 | West | 71 | 9 | 264 | |
| 4 | South | 66 | 11 | 198 | 24 |
| 5 | DACH | 58 | 48 | ||
| 6 | Total | 279 | 46 | 210 |
Week 39 Through yesterday’s close
Five changes ready. Edit a highlighted value before applying.
Two suggested answers, placed directly in the document.
These questions came up in the call, but the current script does not cover them. Review the wording beside the existing document. Accept both, or decide on each insertion separately.
Start with the customer’s question. Use these answers as guidance for the conversation.
Voice can work alongside your CRM, or bring several CRMs into one view. Ask where updates get lost between the meeting and the record.
Offer a joint call with both legal teams. Share the approved security packet beforehand, and agree who will bring the remaining questions.
Use the approved multi-year pricing band. Put the term, annual price, and validity date in the same reply. Ask the account owner to review any exception.
A three-slide proposal and a one-page summary for the partners.
Julie needs something she can forward. The deck uses her words from the meeting, the agreed pilot from Slack, and the approved pricing. The one-pager carries the same offer for partners who prefer a document.
The title uses Julie’s wording. The proposal follows her meeting requirements.
Proposal summary for the partners
Paperwork after every client visit takes time away from the next customer. The team needs the conversation to stay with the account.
One coastal team, two claim types, three weeks. Start after the security review. Agree the success criteria with Julie before kickoff.
The approved annual option is attached to the proposal. Review the pilot with the partners on Tuesday, then confirm the rollout scope.
An answer grounded in the help center and the customer’s account.
Carol wants to add teammates without exposing private notes. The guide answers both parts. This reply explains exactly what changes with pipeline membership.
Hi Carol, You can add both account managers from the pipeline’s member list. They will be able to see its clients and shared activities. Private notes stay private to their owner. Adding someone to the pipeline does not change that. Open the pipeline, choose Members, and add the two teammates. Let me know if you would like a hand with the setup. Alex
Carol Susi · Zendesk · Ticket #1842 · Open
Hi, we have added two new account managers. How do we give them access to the shared pipeline without sharing everyone’s private notes? Thanks, Carol
The right changes go back to the right CRM, with the meeting attached.
Your teams use two CRMs. These updates keep each account in its home system while giving you one place to review the work. Edit a value or leave an item out before applying.
The project, the brief, and the team update, ready together.
The handoff keeps the promises from the call with the people doing the work. Review each step before creating the project and sharing the brief.
Owner: Sarah · Kickoff: Tuesday
Scope, stakeholders, commitments, and the meeting
Brief the delivery team and link the project
Thompson’s pilot covers one coastal team and two claim types. Sarah owns the kickoff. Security review comes before the first live client data.
The project includes the agreed scope, Julie’s meeting, and the success review at the end of week three.
A short weekly update with the numbers and the account risks.
Your previous correction is applied here: closed revenue and open pipeline are separate, and the source date is included. The next actions come from the account records.
Sales update · Week 39 Activity: 279 calls and 46 demos. Closed revenue: $210K. Open pipeline: $1,114K. Watch list: Globex needs the multi-year quote; Acme has the joint legal review on Thursday. Next: account owners to confirm both follow-ups. Source: Sales KPI weekly, through Thursday’s close.
Prepared for #sales-leadership
279 calls · 46 demos. The combined activity from your connected CRMs.
Closed revenue: $210K. Open pipeline: $1,114K. Source date: Thursday’s close.
Globex: multi-year pricing for procurement. Acme: annual quote and legal review. Thompson: partner proposal for Tuesday.
Use the renewal thread as the source and remove the meeting reference.
The unsupported call reference is gone. The reply now follows the exchange you actually had with Piotr and gives him the next step he asked for.
Hi Piotr, Following up on Tuesday’s renewal thread. The updated terms are ready, with one signature line still open. I will send the final PDF today so you can arrange the signature this week. Alex
Piotr Nowak · Outlook · Tuesday
The terms look good. Please send the final PDF so we can arrange the signature. Piotr
