Skip to main content
Back to Read
AI Agents27 April 2026Updated 21 September 20269 min read

Hermes Agent for Sales & CRM Automation (UK Guide 2026)

Four Hermes sales and CRM workflow examples: reactivation reviews, pipeline triage, follow-up drafts and forecasts, with UK marketing eligibility and approval controls.

Gouache painting of a red-haired woman at a small desk holding one printed sheet while a tray of drafts waits beside her.
Editorial illustration.
  1. 01The four workflows worth automating
  2. 02The GDPR/PECR posture for UK businesses
  3. 03What this costs vs alternatives
  4. 04How Ampliflow deploys this for clients

Dormant contacts and incomplete CRM records can hide follow-up opportunities. Hermes can help prepare the work, while a salesperson decides what should happen next. This guide sets out four sales and CRM workflow patterns to evaluate, with approval boundaries and the UK marketing rules to check. The examples are not measured client results or a promise of recovered revenue.

Editorial review: 21 September 2026. Workflow examples below are illustrative; integration and permissions depend on your deployment.

TL;DR:

  • Four CRM workflows worth automating: dormant reactivation, pipeline triage, follow-up drafting, weekly forecast
  • Hermes drafts; the salesperson approves; never autonomous send for cold/dormant outreach
  • For UK businesses: check recipient status, PECR eligibility and the separate GDPR lawful basis before adding anyone to a send queue.
  • Measure model usage, integration work, maintenance and review time before estimating ongoing cost.
  • Pairs naturally with the 5-step database reactivation campaign framework

The four workflows worth automating

  1. 01Workflow 1 — Dormant lead reactivation queue
  2. 02Workflow 2 — Pipeline triage and prioritisation
  3. 03Workflow 3 — Follow-up drafting from sales calls
  4. 04Workflow 4 — Weekly forecast + commentary

Not everything in sales should be automated. The pattern works best when the work is repetitive, evidence-based, and benefits from the salesperson's judgement at the moment of send.

Workflow 1 — Dormant lead reactivation queue

Start here if missed follow-up is a documented problem and the relevant contacts are eligible for marketing.

The pattern:

  1. Hermes runs weekly (Sunday evening) against the CRM
  2. Identifies a candidate segment, then checks permissions, objections and suppression records before drafting
  3. Segments by previous engagement type (warm leads, past customers, churned customers, new-and-cold)
  4. For each eligible contact, drafts a message grounded in their recorded interaction
  5. Queues drafts for the salesperson to approve in the Monday morning review
  6. Salesperson reviews a manageable batch, checking the recipient, claims, relevance and eligibility
  7. Approved messages send via the CRM's normal sending infrastructure

What it replaces: the salesperson's perpetually-unfinished task of "I should follow up with old leads but I never do." It does not replace the salesperson — it removes the friction.

Measure the outcome: track eligible contacts, approved sends, qualified replies, meetings and won work. Compare recovered revenue with the full delivery cost; do not assume a standard reactivation rate applies to your database.

Critical safety constraint: require approval for the exact recipient and message, and repeat suppression checks at send time.

The deeper framework for what to send when is in our 5-step database reactivation campaign guide.

Workflow 2 — Pipeline triage and prioritisation

The pattern:

  1. Hermes runs daily (08:00 London) against active pipeline
  2. Pulls every active deal + recent activity
  3. Scores each deal by stalledness (no activity in 14+ days), urgency (close date within 30 days), and value
  4. Generates a daily pipeline brief: "5 deals need follow-up this week; 2 are at risk of slipping; 1 may need senior intervention"
  5. WhatsApp delivery to the sales lead before they open the laptop

What it replaces: repeatedly searching the CRM for deals with no clear next step.

The metric that matters: whether the brief leads to appropriate action. Track missed priorities and misleading flags as well as time spent reviewing it.

Workflow 3 — Follow-up drafting from sales calls

The pattern:

  1. Sales lead adds approved written call notes, or an authorised transcript from a supported integration
  2. Hermes uses those notes to draft:
  • Follow-up email summarising the call's key points + agreed next steps
  • CRM activity note for the deal record
  • Suggested next-step task with due date
  1. Sales lead reviews the email and separately approves any CRM write before either action happens

What it replaces: preparing the first draft of notes and follow-up tasks after a call.

The benefit to check: whether another team member can understand the deal from accurate, complete notes. Missing information should stay marked as missing.

Workflow 4 — Weekly forecast + commentary

The pattern:

  1. Hermes runs every Friday at 16:00 London
  2. Pulls week-over-week pipeline movement + close-rate trends
  3. Drafts a commentary showing the period, source figures and open questions. Any explanation for a change in win rate is a hypothesis until supported by evidence.
  4. Queues the commentary for review before sharing through an approved channel

What it replaces: assembling the first version of a weekly pipeline summary.

This can support a team without a dedicated sales-operations analyst, provided someone owns the definitions and checks the numbers.

The GDPR/PECR posture for UK businesses

Check who you are contacting and why before creating a send queue. A contact being in your CRM is not permission to market to them.

UK GDPR governs personal-data use. PECR, the Privacy and Electronic Communications Regulations, sets separate rules for electronic marketing. A GDPR lawful basis does not replace a PECR consent requirement.

Recipient or routeWhat to check
Corporate subscribersPECR generally allows unsolicited marketing email to corporate bodies. This can include a named employee's work address; the subscriber's legal status matters, not whether the address starts with info@. Identify the sender and provide a working opt-out.
Sole traders and some partnershipsThese are individual subscribers. Unsolicited electronic marketing normally needs consent or a valid soft opt-in.
Soft opt-inAll conditions must hold: you collected the details during a sale or negotiation, market your own similar products or services, and offered an opt-out at collection and in every message. A past purchase alone is not enough.
Personal dataAssess and document the appropriate GDPR lawful basis, provide privacy information, minimise data and respect objections. Legitimate interests requires an assessment; it is not automatic permission to email warm leads.

See the ICO's electronic-mail marketing rules and business-to-business marketing guidance. Check the current rules for the recipient and channel before launch.

Our cold-email legality guide explains the distinction, while Hermes security and GDPR covers the deployment controls.

Keep a salesperson in the approval loop. They should verify eligibility, relevance, accuracy and the intended recipient before release. Human approval helps catch mistakes; it does not itself make an otherwise unlawful message lawful.

What this costs vs alternatives

Compare the full cost of a working process, including maintenance and review time.

OptionCosts and responsibilities to compare
Self-hosted HermesIntegration, hosting, model usage, monitoring, backups and someone responsible for failures
Your CRM's native automationExisting subscription limits, supported workflows and any additional seats or features
Dedicated sales-engagement platformLicence, onboarding, integration, sending controls and support

Hermes may fit a bespoke workflow, but a native CRM feature can be simpler to maintain. Our production cost teardown is one dated deployment's evidence, not a quote for a four-workflow sales system.

How Ampliflow deploys this for clients

An illustrative four-stage plan, organised under weekly headings. These are planning examples, not a promised delivery schedule. Move on only when the previous stage passes review.

Week 1 — Pipeline triage workflow

Lowest-risk first. Hermes pulls pipeline data daily, generates the morning brief, sends to WhatsApp. Read-only — no outbound communication. Builds trust in the agent's data + analysis quality.

Week 2 — Follow-up drafting

Add the post-call drafting workflow using approved notes. Keep both sends and CRM writes behind explicit approval.

Week 3 — Dormant reactivation queue

Add a small eligible reactivation segment. Record rejection reasons and edits, and improve the source data or instructions before expanding it.

Week 4 — Weekly forecast + commentary

The lightest-touch workflow added last because it benefits from the trust built in weeks 1-3. Hermes generates the Friday commentary; the founder reads it before the weekend.

Total cost at steady state

Agree the scope before estimating cost: which CRM, what data volume, which model, how often jobs run, who reviews drafts and who maintains the integration. Measure these in a read-only pilot before approving broader access.

For dormant-database work, our ReFlow service starts with the audience, permissions and follow-up process. The agent is one possible implementation choice.

Frequently asked questions

Can Hermes integrate with my CRM?

A documented CRM API is a starting point, not proof of compatibility. Check the required endpoints, authentication, permissions, rate limits and audit trail before committing to an integration.

A controlled CSV workflow may be possible where an API is unavailable. It still needs access controls, secure handling and reconciliation before any import.

Does Hermes send messages on my behalf?

Hermes drafts messages. Sending happens through your existing email/SMS/CRM infrastructure after human approval. Hermes is not a sending platform — it's the drafting + queueing + analysis layer that sits in front of your existing tools.

Is autonomous outbound sending safe?

Human approval is the default for the workflows described here. Any proposed automated send needs a separate review of audience eligibility, message rules, suppression checks, error handling and how to stop the system. Calling a list “warm” or “existing customers” does not settle those questions.

What CRM data does Hermes have access to?

Whatever you scope it to. Configure the CRM API user with read-only access to the contact records + activity history needed for the workflows. Don't give Hermes write access to anything other than the activity-note-creation flow that's part of Workflow 3.

What happens to drafts that don't get approved?

Define an expiry rule in the review-queue implementation and test it. For example, you might discard a draft after seven days and require a fresh eligibility check before regenerating it. That is a control to build, not a guarantee provided by a skill's written instructions.

Does Hermes handle multi-language outbound?

Models can draft in several languages, but a fluent reviewer should check the message and local marketing rules. A UK workflow should not be reused in another country on tone changes alone.

How do I prevent Hermes from generating embarrassing or off-brand drafts?

Use documented voice rules, approved examples and human review. Revise instructions deliberately from recurring errors; salesperson edits do not automatically train the underlying model.

Can Hermes work alongside my existing sales engagement tool?

It can, where the tools support the required integration. Define which system owns contact eligibility, suppression, approvals and execution before connecting them.

What should you do next?

Start with one read-only pipeline brief or a small, eligible reactivation segment. Compare its output with the salesperson's judgement, record mistakes and review time, and decide whether it earns a place in the team's routine.

Explore sales automation →

To discuss your own process: Get unstuck →

Hermes setup help

Deployment, skills and day-two reliability

Get help setting up your Hermes agent

We deploy, harden and maintain Hermes Agent for UK businesses — cloud hosting, gateways, skills, approvals, monitoring and recovery included.

Cloud deployment & hardening
WhatsApp, Slack & email
Safe, repeatable skills
Monitoring & recovery
Scope my Hermes setup

Bring the use case or the setup you already have. We will tell you the smallest sensible next step.