Async Quote Approval Workflow for Remote and Distributed Sales Teams

BOTrento Team14 November 20266 min read

Why synchronous approval breaks for distributed teams

Approval meetings assume everyone is free at the same moment. With remote or part-time colleagues, that rarely holds. The usual result is one of three things:

• Quotes queue up until the next weekly call.
• Approval happens in scattered chat messages that nobody can find later.
• The salesperson guesses and sends the quote without sign-off, then fixes it afterwards.

None of these is a people problem. It is a process problem: nobody defined what a complete approval request looks like, who answers it, or how long they have.

The five rules of async sign-off

1. One owner per quote. The salesperson who owns the enquiry owns the approval request until the quote is sent. If you are unsure how to split ownership, see shared inbox vs assigning enquiries.
2. Fixed order of reviewers. Technical check first, pricing second, final sign-off third. Do not ask everyone at once, or you will get conflicting answers.
3. A deadline in hours, not "soon". For example, one working day per reviewer. Write the deadline in the request.
4. Three allowed answers only: approved, approved with changes (listed), or not approved with a reason. No open-ended debate in the thread.
5. A fallback if nobody answers. Decide in advance who covers when the approver is away or silent.

The fixed-order idea is covered in more depth in our piece on a collaborative quoting workflow.

Step-by-step: set it up in a week

1. Define approval thresholds

Not every quote needs every reviewer. Write down which cases need technical review (non-standard scope, new equipment, special logistics) and which need pricing sign-off (discounts beyond your usual range, custom bundles). Standard quotes should need no approval at all.

2. Create approval stages

In Pipedrive or HubSpot, add deal stages such as "Awaiting technical review", "Awaiting pricing" and "Ready to send". If you work mainly from Outlook or Gmail, use labels or folders with the same names.

3. Standardise the request

Use one template (below) so reviewers never have to ask what the customer wants.

4. Set reminders

Every request creates a task for the approver with the deadline. Use task reminders in your CRM; the setup is similar to the one in HubSpot follow-up tasks.

5. Name a deputy for each approver

If the deadline passes, the request goes to the deputy automatically, by rule, not by negotiation.

6. Review weekly

Look at quotes that waited longest and ask why. Usually the request was incomplete or the threshold was too low.

A request template you can copy

Send this as an email, a CRM note or a task description. Keep the format the same every time.

Subject: Approval needed by [day, time, time zone] – [Customer] – [short scope]

Hi [name],
please review the draft quote for [customer]. Link to the draft and enquiry: [link].

What the customer asked for: [2–3 lines]
What is unusual: [non-standard item, discount, deadline]
What I need from you: technical check / price check / final sign-off
Deadline: [date, time, time zone]. If I do not hear back, [deputy name] will decide.

Please answer with one of: Approved / Approved with changes (list them) / Not approved (reason).

Thanks,
[your name]

The line about the deputy is the most important one. It makes silence a decision path instead of a stall.

Common mistakes to avoid

• Approval in chat only. Decisions disappear. Copy the final answer into the deal or enquiry record.
• Time zones left implicit. Always write the deadline with its time zone.
• Too many approvers. Every extra reviewer adds a day. Keep the chain as short as the risk allows.
• No expiry on the quote. While approval is pending, the customer is waiting. Send a short holding message so they know a quote is coming.
• Approving the draft but not the wording. Check the email text that goes with the quote, not only the numbers.

How BOTrento supports async approval

BOTrento Chief of Staff is a managed process for enquiries, quotes and follow-ups. It watches enquiries in your mailbox and uploaded data, and prepares drafts of replies, quotes and follow-ups in four languages (CS, EN, DE, FR). Nothing is sent without human approval: a person on your team reviews and approves every draft, which fits an async model well, because the reviewer can check a ready draft when they are online.

Each working morning it shows a "Today 1+3" overview in the app and by email, so approvers see what is waiting. It also captures promises such as "I'll get back to you by Friday" and reminds you. Meetings and tasks can be taken into Outlook, Google Calendar or iPhone through an iCal link. BOTrento does not send anything itself and does not replace your CRM or accounting; it works alongside them. AI is included in the plan, with a monthly usage limit.

You can see how the flow looks in the process demo. For cost questions, see our answer on what an AI sales assistant costs a small business, and for data handling, the GDPR checklist for AI sales tools. If you work in this space, there are dedicated pages for event and production companies and equipment rental.

The trial runs 14 days free, with no card and no API key of your own. It starts when you first upload data or connect a mailbox, and you get 7 days to prepare. You can start the free 14-day trial and test it on your own enquiries.