Answer the repeat questions
Give your assistant approved business information so it can explain your services and handle routine enquiries.
WhatsApp-first AI sales CRM
Help customers get answers from approved information. Keep their conversations and next steps together. Give your team the context to step in when judgement matters.
Approved answers. Clear human handover.
The Relay Pilot
Test Relay against your real enquiry workflow. Pilot scope and pricing are agreed before you start.
Join the PilotYour customers already use WhatsApp. Keep the conversation, the context and the next step together.
Give your assistant approved business information so it can explain your services and handle routine enquiries.
Bring messages and contact records together, so your team can see the conversation before stepping in.
Keep enquiries, follow-ups and next steps in the same workspace instead of scattered across chats.
Take over a conversation, pause automatic replies and resume the assistant when you’re ready.
Relay’s v1.2 direction connects the work around a conversation: what brought the customer in, what they need and what should happen next.
Use approved information for repeat questions. Keep personal recommendations, negotiation and sensitive decisions with the right member of your team.
The v1.2 handover brings the unanswered question, confirmed preferences, source evidence and next action together, so a customer has less to repeat.
The planned measurement journey follows campaign touches through conversations, appointments and recorded outcomes, with gaps in attribution made visible.
Inside the v1.2 design
A connected workspace designed to help your team act on exceptions, decisions and opportunities. These capabilities are being delivered in stages; confirm availability for your pilot.
Bring advice requests, approvals, failed deliveries, hot leads and due follow-ups into one view. Each item is designed to show the reason, owner, due time and linked evidence, with options to claim, assign or snooze.
Link the contact, company, conversations, appointments, tasks, opportunities and marketing touches. Keep internal case discussions separate from customer messages, with access controlled for each team member.
Find permitted records and supporting messages in one search. Generated relationship summaries are designed to show their evidence and freshness, while confirmed facts remain distinct from an assistant’s interpretation.
Review the trigger, assistant version, approved sources, actions and escalation reason behind a response. Versioned assistants, resumable work and approval controls are designed to make automation easier to inspect.
Planned industry configurations adapt terminology, fields, stages, booking rules and assistant boundaries around a shared Relay core.
Answer approved project questions and keep buyer requirements with the conversation.
Support routine service enquiries and prepare a clearer handover to the authorised adviser.
Help with approved service information and administrative questions before a practitioner takes over.
Keep product questions, customer context and commercial next steps in the same journey.
Industry examples describe the v1.2 design. Booking, forms, reminders and other configured workflows depend on implementation and the agreed pilot scope. Regulated workflows require a review before activation.
v1.2 direction · Planned capabilities
Understand which marketing creates useful conversations, which enquiries progress and where your team needs to intervene.
Tracked links and QR codes are designed to capture UTMs and campaign context before a visitor moves to WhatsApp. Preserve first and later touches where the customer journey can be matched.
A WhatsApp click and a conversation actually started remain separate events. Unmatched activity stays visible.
Offer valid appointment slots for the right person, service and resources. Link a confirmed booking back to the contact and conversation, with rescheduling and cancellation in the planned calendar workflow.
A booking does not imply attendance. Attendance and outcomes need their own records.
Use confirmed activity to support pipeline changes, with a visible reason and human override. Connect appointments, opportunities and recorded revenue to the available source evidence.
Show source confidence and the attribution model. AI-assisted revenue does not establish that AI caused the sale.
Example: a property campaign leads to a WhatsApp enquiry, a qualified buyer books a viewing, and the agent later records the outcome. Relay’s target is to preserve those connections wherever identity and source evidence support them.
New in the v1.2 design · Planned
Turn a new introduction into a reviewed Relay contact, with less retyping and a clear next step.
A mobile-friendly capture flow is designed to let you preview, retake, rotate and crop the image before reviewing extracted details.
Edit the name, role, company, email, phone and other fields. Uncertain values are highlighted. Review possible matches and choose what to update, without silent merging.
The intended result is a confirmed CRM record with its business card source and event context. Open the saved contact and add a follow-up task. CSV export is only a fallback.
Planned capability. A card supplies printed contact details; it does not establish marketing consent or automatically enrol someone in outreach.
The v1.2 design puts permissions, evidence and human decisions around the work Relay can perform.
Classify prospect-safe, client-specific and internal information. The design preserves source revisions and last-confirmed dates, with verification when facts are missing, conflicting or stale.
Pause automatic replies for a conversation and resume explicitly. Planned tool policies and approval steps limit what an assistant may do, with reviewable records of controlled actions.
Planned follow-up sequences check consent, contact rules and suppression. Record a completed purchase, refresh old preferences and configure longer no-contact periods when appropriate.
This page reflects Relay’s v1.2 product design. It is a staged delivery plan, not a claim that every feature is live. Agree the available capabilities, approved answers, human handovers and success measures before your pilot starts. Business card capture, connected workspace features, booking and attribution must be confirmed for your setup.
Start with a manageable enquiry workflow, approved information and a private test before activation.
Set up your business workspace and pair the WhatsApp number your customers contact.
Provide approved business information, set access and reply boundaries, and choose the situations that need a person.
Test answers and handovers privately, confirm which capabilities are available, then agree activation and review measures with your team.
Join the Pilot
For real estate agents, financial services teams, clinics, SaaS businesses and other teams that serve customers through WhatsApp.
Bring a real workflow: project enquiries, appointment requests, service questions or lead follow-up. We’ll discuss the fit, define what the assistant can answer and agree the pilot scope with you.
Request a pilot conversation with Kevin at Aemorph.
Join the PilotOpens your email app. You can also email kevin@aemorph.com.
Version 1.2 is Relay’s product design baseline, covering customer conversations, connected records, human attention, booking, attribution and industry configurations. It also adds planned business card capture. Delivery is staged, so the available pilot scope is confirmed before activation.
Routine factual questions supported by approved information within its configured scope. Missing, conflicting or stale information should lead to verification. Personal advice, suitability, negotiation and other judgement-heavy questions stay with the responsible professional.
Yes. Take over the conversation to pause automatic replies, then resume the assistant explicitly when you are ready. The v1.2 design adds richer handovers with confirmed context and supporting evidence.
The planned attribution workflow captures campaign touches through tracked links and QR codes, then links them to conversations, appointments, pipeline and recorded revenue where evidence supports a match. It separates clicks from started conversations and shows inferred or unknown sources clearly.
That is the intended v1.2 flow after human review and duplicate resolution. It is planned, not a completed release claim. A confirmed save must open the actual Relay contact; downloading a CSV is a fallback and is not treated as a CRM save. Scanning a card does not grant marketing consent.
The v1.2 design separates confirmed facts, original history and generated summaries. Summaries carry evidence and freshness cues. Internal discussions remain separate from customer messages, and search, linked records and memory follow access permissions.
Planned industry configurations adapt labels, fields, stages, booking resources, templates and guardrails. A clinic may need a practitioner and room; a viewing may need agent time, property access and a travel buffer. Each setup uses the same underlying customer journey.
Pilot scope, pricing and support are agreed before you start. Send an enquiry so we can discuss your workflow and confirm which capabilities are ready for it.