Digital customer journey design · Sales
A customer should see the right next step and never receive a reminder for work already done.
A business buyer submits documents through your app, receives an email asking for them again, then gets a WhatsApp reminder from the salesperson. Your team sees separate systems. The buyer sees your business asking for the same thing twice.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

In one paragraph
Digital customer journey design sets out the app notifications, WhatsApp messages, emails, and SMS a customer receives between human conversations, including what starts and stops each message. GullySales maps your existing messages, writes the sequences, and builds supported flows in your current tools, with clear points where your sales or service team takes over.
The same problem affects a hotel booking or a wealth management account opening. A confirmation needs to reflect what has actually happened, and a reminder needs to stop when the customer acts. A question needs a person, not another scheduled message.
GullySales designs these digital steps around the records your tools can use. The work covers message content and the rules behind it, without replacing the conversations your team needs to have.
Who it is for
This is written for you if these sound familiar.
- B2B firms whose sales and service teams send overlapping messages during account setup or renewal
- Wealth management firms with app onboarding and email updates built separately
- Banks and lenders managing document requests or repayment reminders across several tools
- Hotels and paying-guest operators typing booking confirmations and arrival instructions by hand
- Companies adding a digital channel without wanting another disconnected message sequence
Not for
It is not the right fit if.
- Your customer contact is entirely offline, with no digital steps to design.
- You need the full customer experience reviewed first, including offline interactions. Customer experience strategy and journey mapping is separate work.
- You want broadcasts to a purchased list rather than messages based on permission and a genuine customer need.
The problem
Does this sound like your business?
Common situations this work addresses.
“Different instructions on different channels”
The app asks for one document while an old email asks for another. Your team has to explain which instruction is correct.
“Routine messages stuck with one person”
A booking confirmation waits until someone has time to type it. When that person is absent, nobody knows which customers are still waiting.
“Reminders after payment”
The payment record changes, but the message sequence does not. Customers receive another request and contact your team to check whether their payment was received.
“Replies without an owner”
A customer replies with a pricing question or a complaint, but the flow keeps running. There is no agreed point at which a salesperson or service colleague takes responsibility.
Choose the right scope
Start with the work your business needs.
Document collection before activation
A lender or B2B account team needs to show what remains outstanding. The flow requests missing documents and hands questions to a person, using completion records to stop repeat requests.
Booking confirmation and arrival
A hotel or PG operator needs guests to receive the right confirmation and arrival instructions. The sequence follows booking status, with a handover for changes that staff must approve.
Renewal reminder coordination
An account owner needs reminders to reflect renewal status. This scope coordinates digital prompts and stops them after confirmed renewal; negotiation and the wider renewal management process remain separate.
New channel introduction
Your app is adding notifications while email and WhatsApp already carry updates. This scope decides which channel handles each step and removes overlapping messages before the new sequence goes live.
What we do
The work we can include.
Each deliverable and the purpose it serves. Your written scope confirms what is included, who is responsible, and what it costs.
Digital touchpoint inventory
A record of current messages by channel, sending tool, and customer stage. Your team checks it against live messages to identify duplicates and missing steps.
Journey flow diagrams
A sequence showing entry events, waiting periods, and exit conditions. Each branch shows what happens when a customer acts, replies, or does nothing.
Message copy and templates
App notification text and channel-specific message copy for the agreed flows. Your team checks the instructions, links, and wording before templates are submitted for any required approval.
Permission and suppression rules
A record of where permission is captured and which contacts must be excluded from each sequence. Your team reviews opt-outs and dispute-related pauses before launch.
Human handover rules
Written conditions for stopping automation and assigning a reply to a named role. Your sales or service lead checks who receives each type of question and what context accompanies it.
Configured flows in existing tools
The agreed sequences built where your current platforms support them. You review the working setup against the approved flow, with unsupported connections identified rather than assumed.
Test record and message limits
Test results for timing, completion events, and handovers, alongside agreed sending limits. Test contacts show whether a completed action stops further reminders and whether overlapping flows send duplicate messages.
How the result is measured
- Delivery, reads, and link clicks by channel, treated as activity rather than sales
- Customers completing the intended stage
- Replies handed to the responsible person and time to response
- Qualified renewal or additional-order opportunities accepted by sales
- Completed orders or renewals linked to the journey where records allow
- Opt-outs, complaints, and reminders sent after completion
Recorded as a baseline before work starts, so every later report has an honest comparison.
Marketing and sales together
Pass the customer's question to sales with the journey context.
A reply about price or renewal terms should stop the routine sequence and reach the responsible salesperson. The handover record identifies the customer, their current stage, the last message, and the question requiring an answer. Sales records whether it became a qualified opportunity or a completed order; a read receipt does not count as either.
Decisions to make before the work starts
Event and data availability
The flow depends on reliable status records. If your app cannot share a completed action, a manual update or separately scoped connection is needed.
Platform and review dependencies
Tool access, sending permissions, and your approvals affect what can go live. Required platform reviews sit outside GullySales' control.
Journey complexity and exclusions
Branching paths and inconsistent customer records affect the effort required. Full app development, wider customer research, and running your sales or support desk are not included unless separately scoped.
This or a nearby service
Which piece of work fits your situation.
These services sit close to each other. The line between them, in plain words.
- Customer experience strategy and journey mapping
- Choose customer experience strategy and journey mapping when you need the whole customer path reviewed, including offline steps and department gaps. Choose digital customer journey design when you want the app, WhatsApp, email and SMS messages themselves designed and built.
- WhatsApp marketing and automation
- Choose WhatsApp marketing and automation when your work is mostly in WhatsApp, with replies and follow-up for enquiries. Choose digital customer journey design when messages cross several channels and the main problem is what starts, stops and hands over each one.
- Marketing automation
- Choose marketing automation when you want rules that respond to enquiries, bookings and silence with approved messages. Choose digital customer journey design when you first need the whole sequence mapped, including stop conditions and the point where a person takes over.
A sample of the output
A journey message map shows what each message is, what starts it and what stops it.
Each row is one message in a customer journey. Read across for the channel, the event that sends it, the event that cancels it, and who takes over if the customer replies.
| Message | Channel | Starts when | Stops or hands over |
|---|---|---|---|
| Booking confirmation | Booking is entered in the system | Customer cancels, or arrival is recorded | |
| Document request | Booking needs papers not yet received | Papers arrive, then the front desk takes over | |
| Payment reminder | SMS | Invoice is marked as unpaid | Payment is recorded, or accounts are contacted |
| Arrival instructions | Appointment day begins | Customer arrives or asks a question | |
| Follow-up after visit | App notification | Visit is marked complete | Customer replies, then service lead steps in |
Before we start
What we need from you.
The work depends on these. Each says why it is needed and what happens when it is missing.
- A list of messages you send now
- We start from what customers already receive across apps, WhatsApp, email and SMS. Screenshots or exports are fine. Without the list, duplicates and conflicts are missed and new messages repeat old ones.
- Access to the tools that send them
- We build flows in your existing tools, so we need administrator access or a named person who has it. Without it, we deliver the design and your team must build it.
- Events recorded in your system
- A message can only stop when your records show the event, such as payment or arrival. Tell us what is captured. Where an event is not recorded, that message cannot stop on time and is left out.
- Consent records for each channel
- We need to know who agreed to which kind of message, and where that is stored. Customers without clear permission are excluded. Regulated businesses must also get wording cleared by their own adviser.
- A named owner for hand-offs
- When a customer replies, a person must take over. Name who picks up each type of reply. If nobody is named, the message flow ends in silence and the customer is left waiting.
How it works
How the work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Starting journey selection
You choose the customer stage causing the clearest problem, such as document collection or renewal. We agree its boundaries and the person responsible for approving changes.
- 2
Records and tool review
Your team shares current messages and relevant records, along with access to the sending tools. We check which events are available to start or stop a flow.
- 3
Flow and ownership approval
You approve the proposed sequence and channel choices. Sales and service owners confirm the handover points before configuration begins.
- 4
Copy and permission approval
Your team signs off message wording and permission handling. Regulated firms arrange their own compliance review, and platform approvals are completed where required.
- 5
Testing and release decision
The configured flow runs through test cases, including a completed payment and a customer reply. You approve release after reviewing the results and any unresolved limits.
- 6
Results review and changes
We compare results with the baseline recorded before work starts. Reporting frequency and the process for approving later changes are agreed in writing before work starts.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales process design, at stage 0, foundation. The audit comes before it, and sales management keeps it running.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2 · you are here
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
Do we need new software or a new app?
Can we start with one customer journey?
Can you stop reminders as soon as someone pays?
Who checks consent and financial-service messages?
How is this different from WhatsApp automation or onboarding?
How do we agree the cost and scope?
By industry
Digital customer journey design, written for your industry.
Related services
Often bought with this, or instead of it.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.