Recommend
Tandem researches, analyses, prepares, drafts and recommends. A human reviews, decides and approves.
Useful for new workflows, customer communication and commercial decisions.Human approval
AI does the groundwork. You decide what happens.
Tandem can research, prepare, recommend and automate routine work while routing important actions to the right person for approval.
Control is configured workflow by workflow.
- PTandem finds, researches and qualifies
- →Recommendation Move Acme Ltd to Qualified
- HHuman approvalDecision stays with your team
- ✓Action CRM updated only after approval
Three levels of autonomy
Start controlled. Increase autonomy when you're ready.
Assist
Defined low-risk actions can happen automatically while consequential actions route for approval.
CRM enrichment, reports and tasks can differ from stage changes, replies or merges.Automate
Trusted workflows can perform approved routine actions automatically while unusual cases escalate.
Scheduled reporting, routine data updates and recurring admin.Autonomy is configured per workflow, not switched on for the whole business at once.
Illustrative permission setup
Different actions. Different levels of control.
These settings are examples, not universal rules.
ActionAuthority
Prospect researchAutomatic
CRM enrichmentAutomatic
Create internal taskAutomatic
Prepare meeting briefAutomatic
Qualify leadApproval required
Change pipeline stageApproval required
Draft external emailAutomatic
Send external emailApproval required
Merge recordsApproval required
Delete recordsHuman only
Commercial commitmentHuman only
Sensitive decisionHuman only
Decision context
Don't approve a black box.
The person approving should understand what Tandem is recommending and why.
Approval routing
Not every decision belongs with the same person.
Tandem can route a decision to the person who owns it; exact role behavior depends on implementation.
Sales · Lead qualification→ Sales Director
Operations · Onboarding exception→ Operations Manager
CRM · Duplicate merge→ CRM Owner
Commercial · Pricing decision→ Founder / Commercial Director
Approval queue
See what is waiting for a decision.
Fictional examples show the actor, proposed action, confidence and time waiting.
Inside the workflow
Approvals should be part of the process, not an afterthought.
Trigger→Tandem work→Approval gate
Approve → CRM updated
Review → Human edits / checks
Reject → No stage change
Approve
The recommendation is accepted.
Review
A person inspects or modifies it.
Reject
The action does not continue. Feedback may inform later operator-led tuning.
Confidence thresholds
Uncertainty should create review, not false confidence.
Thresholds are configured around the workflow and risk involved.
Exceptions
Unexpected situations should surface, not disappear.
The unusual cases are often where human judgement matters most.
Missing informationReview
Conflicting recordsReview
Possible duplicateApproval
Low confidenceReview
Integration failureException
High-value opportunitySenior approval
Sensitive requestHuman only
External communication
Customer communication can stay behind approval.
Tandem does not need unrestricted authority to email customers or prospects.
Draft automatically. Send only when authorised.
- Inbound request
- Tandem gathers context
- Draft reply prepared
- Human reviews
CRM changes
Not every CRM update carries the same risk.
Lower-risk · potentially automatic
Approved enrichment
Internal task
Research evidence
Higher-risk · approval may apply
Merge records
Change stage
Disqualify / delete
Change ownership
Final authority depends on client rules and implementation.
Commercial decisions
Some decisions should simply stay human.
PricingDiscountsContractsHiring / firingLegalFinancial commitmentsStrategy
Tandem prepares context. The accountable person decides.Illustrative workflows
Controlled approval across Sales, Admin and Operations.
Sales qualification
- Hunter researches Acme Ltd
- Piper scores against ICP
- Recommends Qualified · 84%
- Sales Director reviews
- Approves
- Scout updates CRM
Duplicate merge
- Scout detects two records
- Acme Ltd / ACME Limited
- Match confidence 96%
- CRM owner reviews
- Approves
- Records merged
Onboarding exception
- Required document missing
- Workflow pauses
- Document received
- Tandem recommends continue
- Operations Manager approves
- Workflow resumes
Activity history
Know who approved what.
- PiperQualification recommendation created
- SarahApproved
- ScoutCRM updated
- ScoutDuplicate merge created
- TomRejected
Important actions should be attributable and reviewable.
Delegation
Approval shouldn't depend on one person always being available.
- Primary approver
- Unavailable / timeframe exceeded
- Backup approver or escalation
Useful for qualification, exceptions, merges and customer responses. This is explanatory UI, not a live role system.
Approval rules
Build the rules before the automation.
WorkflowExternal sales email
RuleDraft automatically
SendApproval required
ApproverSales owner
Escalate afterConfigured timeframe
Sensitive topicSenior review
Autonomy by workflow
One business can run several autonomy levels at once.
Authority is defined at workflow and action level.
Gradual autonomy
Earn autonomy. Don't assume it.
A workflow gains authority only when performance, rules and client comfort justify it. Changing authority requires human approval.
- New workflowRecommend only
- TestedAssist
- ObservedSelected actions
- AlwaysExceptions escalated
After rejection
A rejected recommendation shouldn't disappear.
- Recommendation rejected
- Reason captured
- Workflow stops
- Operator review / improvement opportunity
Wrong matchInsufficient evidenceWrong stageMissing context
This can inform operator-led rule or prompt improvement; it is not autonomous model training.
Permissions and approvals
Two controls working together.
An approval screen should not be the only thing preventing a forbidden action.Connected controls
Approval can sit between connected systems.
Connected workflows do not have to be fully autonomous workflows.
Explore Tandem integrations →Email→Tandem→Approval→CRM
Implementation boundaries
You define the boundaries.
These decisions are part of implementation, not something guessed later.
Access
What Tandem can read and write.
Authority
What is automatic, approved or never allowed.
Ownership
Who approves and who acts as backup.
Uncertainty
What happens when confidence is low.
Exceptions
What happens when normal flow breaks.
Visibility
What should be logged and reviewed.
Start with the work
Not sure where you would want human approval?
The free assessment identifies repetitive work and gives an initial view of where AI support may fit.
Take the free Tandem AssessmentSee the wider system
Controlled by design.
Explore how Tandem is implemented around your processes and people.
See how Tandem worksApprovals FAQ
Questions about human control.
Authority is configured explicitly.
Does Tandem automatically send emails?
Not by default. External communication can remain behind approval unless a tested workflow is explicitly authorised.
Can I require approval for every action?
Yes. Tandem can begin in a recommend-first mode.
Can some workflows run automatically while others require approval?
Yes. Autonomy is configured per workflow and action.
What happens if Tandem is unsure?
Low-confidence or unusual cases can route for human review.
Can Tandem change CRM records automatically?
Low-risk approved updates may be automated; higher-risk changes can require approval or remain human-only.
Can we increase automation later?
Yes, after testing and explicit client approval.
Can Tandem override a rejected action?
No. A rejected recommendation does not continue unless a person takes a new action.
Can approvals be audited?
Important activity can be recorded with actor, action, time and outcome according to the implementation.
Controlled delegation
More automation doesn't have to mean less control.
Take the free Tandem Assessment and see where AI could support your team while keeping the right decisions with the right people.