Skip to content
Hermia← Back
Hermia in action

See the detail.
Before the next move.

Choose your CRM and explore the conversation, the prepared record and the context your team receives.

ConversationsRecordsCalendars
3 pathways to explore

Supplied demonstration media and process previews. Each view explains what is shown; your account connections, questions and permissions are configured for your business.

Want to see how the same principle fits your industry?

Explore the industries
← All CRM examplesSimpro / Supplied demonstrations

See the conversation.
See the Simpro handoff.

From a question on WhatsApp to a record your office can review. Explore supplied examples of the conversation, prepared lead and scheduling context.

Supplied recordings alongside labelled edited conversation, CRM and calendar illustrations. Message wording, roofing headings and sample calendar labels are illustrative edits, not live-account or setup changes. Examples can come from different sessions; each business’s actual setup is configured and tested.
Illustrative Simpro-pathway conversation showing two consecutive customer messages and one response using their combined context
Illustrative conversation showing intended double-message handling. This is not a recorded production test or a guarantee of error-free processing.
01 / Two consecutive replies

Two messages.
One enquiry.

Customers do not always put every detail into one message. This illustration shows an issue in the first reply, then a name and location in the next, followed by one acknowledgement that uses the combined context.

  • Keep the issue and the later identifying details together.
  • Use the context from both replies in the next question.
  • Test message-order handling in the actual configured setup.
Edited illustrative WhatsApp example showing incomplete-message clarification
Edited illustrative conversation, not an unchanged live transcript or live-setup fix.
02 / When a reply is incomplete

An unfinished message.
A clear next question.

A cut-off message is not a complete enquiry. This edited example illustrates the intended follow-up: ask for the missing issue, keep the reported roof leak in context and collect a preferred time without treating it as a confirmed appointment.

  • Invite the customer to complete an unfinished message.
  • Keep the reported issue in the follow-up question.
  • Request a preferred time; let the authorised team confirm availability.
Edited illustrative roof-enquiry conversation with varied follow-up wording
Edited illustrative conversation; customer and assistant wording is varied for clarity.
03 / When the answer is still vague

Same subject.
A different next question.

When a reply still leaves the roof material unclear, make the next question more helpful—not a copy of the previous one. This edited example varies the wording, asks for the missing detail and offers a photo as another way to provide context.

  • Use different wording when the same question is not helping.
  • Ask for the specific detail the enquiry still needs.
  • Offer a photo or voice message as an alternative to typing.
Edited illustrative roofing demo: the business heading is corrected; the source enquiry details are retained. This is not a live-account change or untouched source recording.
04 / The CRM record

A brief your office can work with.

The useful detail should not stay buried in a chat. An approved Simpro handoff can carry the reported issue and relevant notes into the record your team uses, ready for a person to review instead of retyping the whole conversation.

  • Keep the customer’s account of the problem attached to the lead.
  • Give descriptions and notes a clear purpose.
  • Let your team assess the work and decide the next step.
Illustrative Simpro calendar with Customer Availability above the times and fictional names and jobs below
Edited illustrative Simpro calendar: Customer Availability heading, time range, then the sample customer name and job description. These are not live bookings.
05 / The calendar context

Give availability a place to land.

A preferred time is useful only when the right people can see it. Hermia captures the customer’s preferred time alongside the enquiry, for your team to confirm. With Simpro or a Google or Outlook calendar connected, Hermia books it in once your team confirms, or straight away if you choose automatic booking.

  • Collect the customer’s preferred time.
  • Keep business hours and approved scheduling rules visible.
  • Confirm the booking through the authorised process—not by assumption.
Prepared enquiry docket containing the reported issue and supporting details
Supplied Simpro-pathway prepared-docket example with the reported issue and supporting context.
06 / The team handoff

The same context. In the right hands.

Your team should not have to piece together a message, an image and an email to understand one enquiry. A prepared docket brings the available detail together and routes it to the recipients your business chooses.

  • A concise reported-issue summary.
  • Supporting evidence kept with the same enquiry.
  • Approved recipients, with access and delivery defined by your business.
More from this example

More detail.
At your own pace.

Open a full image or play a recording. Explore the part of the enquiry that matters to your team.

14 examples

Two replies, one enquiry

Explore the combined context in this double-message illustration.

Illustrative intended behaviour, not a recorded live test or zero-error guarantee.

When the message is cut off

Explore the illustrative context-preserving follow-up.

Edited illustrative conversation, not a live-setup fix.

A more useful roof question

Explore the varied follow-up wording.

Edited illustrative customer and assistant wording.

Availability on the schedule

View the full supplied resource-calendar example.

Edited illustrative calendar with Customer Availability above the times and fictional names and jobs underneath. It is not a live booking confirmation.

Customer context in Simpro

Explore the edited customer-record preview.

Edited Simpro customer preview with a fictional example.com email.

The right site, with the enquiry

Explore the supplied site-record layout.

Edited illustrative Simpro site preview.

A clear introduction

Watch the supplied roofing-pathway introduction.

Supplied conversation recording, shown only in the Simpro pathway.

From a vague reply to useful detail

Watch the supplied clarification sequence.

Supplied conversation recording, shown only in the Simpro pathway.

Explore the prepared brief

See the reported issue and evidence together.

Supplied prepared-docket recording, restricted to the Simpro pathway.

A next-step question

Read the supplied example estimate and response.

Demonstration estimate only; not Hermia pricing or a final job quote.

Capture a preferred time

Read the supplied roofing availability exchange.

Supplied Simpro-pathway conversation; the team confirms the appointment separately.

The lead at a glance

Inspect the reported fault and enquiry notes.

Edited Simpro lead preview with a fictional example.com email.

A structured record preview

Explore the supplied record layout.

Illustrative supplied record layout, shown only in the Simpro pathway.

Keep the supporting media

Explore the supplied evidence view.

Supplied submitted-media recording, restricted to the Simpro pathway.
Your operating standard

Like the direction?
Configure your own.

Your channels. Your questions. Your recipients. Define the process you want Hermia to follow for your business.

Configure Hermia Ask a question ↗
← All CRM examplesYour CRM / Tailored scope

Your system.
Your operating standard.

Explore a separate property-enquiry illustration and an original generic CRM workspace concept, then scope the connection your business actually needs.

These are original illustrations, not proof that every CRM is connected. Specialist industries, sensitive data, messaging channels and calendar features require appropriate scoping and permissions.
Distinct illustrative property enquiry showing consecutive customer messages
Illustrative property-enquiry conversation. The actual CRM connection and message rules require configuration and testing.
01 / Your own enquiry standard

Different work.
A distinct conversation.

This property-office example has its own customer, request and wording. Two consecutive replies provide the issue, apartment and customer name before the illustrative acknowledgement uses them together.

  • Define the questions your industry and team need.
  • Keep context from separate replies with the same enquiry.
  • Configure and test the actual CRM and channel connection.
Original generic CRM concept with enquiry pipeline, contact fields and preferred time
Original illustrative CRM concept, not a screenshot of Simpro, AroFlo or a live connected account. All sample contacts are fictional.
02 / Your CRM destination

A CRM workspace.
Not another system’s footage.

This original CRM concept shows enquiries, contacts and a preferred time in one familiar workspace. It illustrates the kind of destination your business may use; it does not claim that an unlisted CRM is already connected.

  • Agree the actual record destination and permissions.
  • Map the enquiry context to the fields your team uses.
  • Review and test the proposed connection before go-live.
More from this example

More detail.
At your own pace.

Open a full image and explore this pathway’s examples. Explore the part of the enquiry that matters to your team.

2 examples

A distinct property enquiry

Explore the apartment and request context from two replies.

Illustrative property conversation; the actual CRM route requires configuration.

Your CRM workspace concept

Explore enquiries, contact fields and a preferred time.

Original generic CRM illustration; not a real connected account.
Your operating standard

Like the direction?
Configure your own.

Your channels. Your questions. Your recipients. Define the process you want Hermia to follow for your business.

Configure Hermia Ask a question ↗
Demonstration image