Platform / Follow-up and workflows
Building · target December 2026Used for follow-up and next steps
Approve the follow-up, then let it run.
New leads, meetings to confirm, quotes to chase: the same follow-up every day. Pinpoint will draft that work and run it only where a manager approves.
Danny offered Saturday 12:30 at 0:58. Trevor was tentative at 1:12, and Danny promised to text the details at 1:16. No confirmation is visible in this thread.
What actions and workflows are
Actions and workflows are the follow-up a sales team runs after a conversation: lead response, meeting confirmation, no-show recovery and quote follow-up. Pinpoint is building approved actions first, with a target of December 2026, and bounded workflows after them. Pinpoint will draft the action and the message, a manager will approve it, and anything that runs unattended will run only inside the scope, the limits and the permissions your team sets, with a receipt for each step.
Building, with a target of December 2026. Approved actions are not available yet; Pinpoint proposes next steps for a person to carry out.
How it will work
- 01
The conversation sets it off
A workflow will start from something that happened in a conversation: a lead that came in and went unanswered, a meeting set but never confirmed, a quote sent with no follow-up planned. The trigger will always point back to the moment behind it.
- 02
The action is drafted
The next step will be written out in full before anything happens: the message, who it goes to, when it sends and what it refers to. A manager will read the draft the way they would read a rep's text before it went out.
- 03
A person approves
Approval will be the gate. A manager will approve one action, approve a sequence, or allow a routine one to run inside set limits. Every permission will be reversible, and turning one off will stop the next step rather than leaving something half sent.
- 04
Receipts close the loop
Every action will leave a record: what was proposed, who approved it, what was sent and what came back. A sent message and an answered customer are different things, and the receipt will say which one happened rather than reporting the task as done.
What a manager will see
- A drafted reply for each new lead, waiting for approval.
- Meeting confirmations queued for the times that were set.
- A no-show recovery step proposed the morning after.
- A receipt for every action: proposed, approved, sent, answered.
Questions about actions and workflows
Something else? Ask on a walkthrough.
Will it message customers without me?
No. Every action will start as a draft you can read: the message, the recipient, the timing and the conversation it came from. It will go out when a person approves it, or inside a routine a manager has deliberately turned on with limits. Permissions will be set at onboarding and can be narrowed or switched off at any time.
Which workflows will it run?
The routine ones every sales team already runs by hand: answering a new lead, confirming a meeting, calling a no-show back the next morning, following up a quote that has gone quiet. The point is not to invent a process. It is to make sure the one you already have happens every time.
Does a finished workflow mean the customer was reached?
No. A receipt will say a message was sent and whether anything came back. Sent is not read, read is not answered, and answered is not a meeting or a sale. The record is built to keep those states apart so nobody reports a task as done when the customer never heard from anyone.
Can I use workflows now?
Not yet. For now Pinpoint proposes the next step and a person carries it out. Approved actions are building, with a target of December 2026, and bounded workflows that run inside the permissions you set come after. No part of the product sends a message to your customers on its own.
What if I want a person to do a step?
Then a person does it. A workflow will be built from steps you choose, and any step can be an assignment to someone on your team rather than something Pinpoint sends. Deciding what to automate and what to keep human is a management decision, and the permissions are built to let you draw that line where you want it.
Go deeper
Lead response in the first five minutes: what the first call and text should contain
The first five minutes are won by a short call that names what the customer asked about and offers a time, followed in the same minute by a text the customer can answer with one thumb.
Follow-up and workflows · 7 min readAn appointment confirmation sequence that holds
A confirmation sequence holds when every touch delivers something instead of asking whether the customer is still coming, and the same named person sends all of them.
Follow-up and workflows · 8 min readWhat to automate in sales follow-up, and what to keep human
Automate the work that has one correct answer and creates no commitment, and keep anything that negotiates, reads emotion or promises something with a person.
Follow-up and workflows · 7 min read
See it on your own calls and texts.
A 30-minute walkthrough with a person who can answer questions, then a free review of your own calls.