Update the CRM by talking to it
Dictate what happened and review the change before it lands. The assistant proposes; you press Apply.
The job
“I want to get what I know into the CRM without opening six fields after every call.”
- Sales reps
- Customer success managers
- Sales managers
Every organisation with a CRM has the same complaint from two directions. Leadership says the data is unreliable; sellers say maintaining it is not selling. Both are right, and the disagreement is really about who should pay the cost of structured data — the person who has the information, or the person who needs it later.
Dictating is the version of that bargain sellers will actually keep, because the cost drops to roughly the cost of saying what happened out loud. What makes it safe is that speech is not the write: the assistant turns what you said into a specific, readable proposal, and a person releases it. Nothing is guessed into your CRM on the strength of a transcript.
What it moves
- CRM update completion
- Time spent on administration
- CRM data completeness
The division of labour
What RevTech does, and where you decide
In the product
How to do it
- Step 1 of 4
Open the assistant from anywhere
The assistant is a persistent surface rather than a page, so it is available wherever you are. The collapsed launcher is itself the composer row: start typing, or use the microphone if speaking is easier. It stays usable while you have an account, deal or contact record open, which is exactly when you most want it.
- Step 2 of 4
Say what happened, in your own words
You do not have to name fields or speak in a format. Describe the call the way you would to a colleague — who you spoke to, what changed, what you agreed to do next — and let the extraction do the mapping. Live captions show what was heard, so a mis-hearing is visible immediately rather than at the review step.
- Step 3 of 4
Read the proposal before you apply it
Every write comes back as an editable, human-readable proposal: this record, these fields, these values. Read it as you would read a colleague’s draft of your own note. Edit anything that is close but not right, and press Apply to commit it. Closing the panel without applying leaves your CRM exactly as it was.
- The proposal names the record, so a mis-targeted update is caught before it lands
- Editing the proposal is faster than re-dictating
- Nothing applies itself, and nothing applies on a timeout
- Step 4 of 4
Use it for the small things too
A dictated task becomes a card in your own queue, which keeps one list as the whole list. That is the habit that makes the rest of the queue trustworthy: the moment people keep a private list alongside it, the shared one stops being the whole picture.
What arrives
What this puts in your Action Center
| Item | What is prepared | How it resolves |
|---|---|---|
| ManualTask | Nothing — this is the item you created by speaking | Acknowledge |
Where this is today
Which CRM fields the assistant may update, per kind of update, is an administrator setting. That settings surface is not backed by the platform yet, so in a production tenant the mapping is configured with RevTech rather than edited in the app. The dictation, the proposal and Apply all work as described.
What to take away
- Speech is not the write. Every change is a proposal you read and release.
- Describe what happened; do not try to speak in fields.
- Watch the live captions — a mis-hearing caught there never becomes a wrong proposal.
- Dictated tasks land in the same queue, which is what keeps one list the whole list.
Go deeper
The material behind this
Try the demo.
See agents carry the repeatable work of GTM across sales, marketing, customer success, and RevOps. Every action prepared, reviewed, and recorded. Fictional data, real product.
Explore the demo