Temples · Buyer journey
Trace the path from a search for the deity to a booked seva.
The devotee journey runs from a search for the deity and the town, through the timings and the festival calendar, to a booked seva or an offering sent from another city. GullySales maps that path for your temple and finds the point where a devotee gives up and closes the page.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What buyer journey means
The buyer journey is the sequence of steps a customer actually takes, from first hearing about you to deciding to buy, which is rarely a single visit or call. GullySales maps this sequence for your business and checks that something useful happens at each step instead of only at the final call.
Last updated 14 Nov 2026.
For temples
Where it usually goes wrong, and what we would do.
“The journey starts weeks before the festival, not on the day”
A family travelling for the brahmotsavam books their tickets well ahead. They are looking for the dates, the timings and whether a seva can be reserved, and a calendar not yet published sends them to a temple whose calendar is.
“A local devotee and a family abroad travel different paths”
Somebody in the next street checks nothing and walks in. A family in another country needs the date, a payment page that works, a receipt, and afterwards some sign that the ritual was performed.
“Journeys end at a phone number”
A page that answers a question with call the office loses the devotee reading it at eleven at night, or from another time zone, or who simply will not ring a stranger to ask the cost of an archana.
What we do
What we deliver for temples.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
The devotee's path written out, search to offering
The steps a devotee takes, named and put in order, from the first search to the receipt for a seva or a donation.
Result: The trust can see the journey instead of guessing at it.
The drop-off points found in your own pages
Where visitors leave: the timings page, the seva list, the payment step or the receipt, counted rather than assumed.
Result: You know which page is losing the visit.
A separate path for the family living away
What an out-of-town or overseas family needs at each step, including the confirmation that the ritual took place.
Result: A distant family is planned for rather than improvised around.
A festival path prepared ahead of the calendar
What a devotee needs in the weeks before a brahmotsavam: dates, travel information, accommodation and the seva booking page.
Result: The information exists before devotees start planning.
A first-time visitor path
Where to park, which entrance, what is expected of a visitor, whether photography is allowed and how long darshan takes.
Result: A first visit is clear enough that the family comes again.
How the result is measured
- Drop-off rate by step
- Time from first contact to sale
- Steps with no content
Recorded as a baseline before work starts, so every later report has an honest comparison.
Stages of the devotee's journey
From a search for the deity and the town to a receipt for a seva, the steps a devotee takes.
- The wish to visit or give
- A festival, a vow, a child's naming or an anniversary brings the temple to mind. Put the festival calendar and the next utsavam dates on the home page.
- Searching for timings
- The devotee searches the temple name and opening hours on a phone. Keep the Maps listing and the website timings identical, and note any change for festivals or eclipses.
- Choosing a seva
- A family looks at what sevas are offered and at what amount. Publish the list with each seva's name, the amount, what the devotee receives and the days it is performed.
- Booking and payment
- Visitors give up here, especially those abroad. Ask only for name, nakshatra and gotra where the seva needs them, the date and a contact, and show the payment options.
- The visit or the sankalpa
- Local devotees come in person while a family abroad wants the seva done in their name. Say how the prasada is handed over or sent, and how the devotee is told the seva was performed.
- Receipt and the next utsavam
- The devotee expects a receipt and an acknowledgement. Send it with the temple's name and the seva date, and note the devotee for a reminder before the next festival.
Who it is for
This is written for these temples.
- Ancient and heritage temples with high pilgrim footfall
- Neighbourhood and community temples
- Temple trusts managing more than one shrine
- Shrines with a strong NRI devotee base overseas
- A temple known for one festival or utsavam
- Temples running annadanam and community welfare programmes
Before you decide
When this may not be the right fit.
- You have not looked at how devotees actually find the temple today, so any map of the journey would be a guess.
- The temple has no booking or donation step yet, and the journey would end at a page with no next action.
- You want to map the journey for visitors who arrive only by word of mouth and never search online.
Before you decide
Agree the work. Know how to judge it.
Devotee journey for temples: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
Write the decision the research must support, such as entering a market or choosing a buyer group. Separate what you know from sales records from what the team currently assumes.
Make the scope clear
Agree which buyers to speak to, which sources to review, and what access you can provide. Include lost enquiries and people who chose another supplier, where they are willing to take part.
Check the work in use
Look for source dates, sample limitations, and evidence that disagrees with the preferred answer. A recommendation should show how it follows from the findings.
Know when to change course
Do not treat a few positive conversations as proof of demand. Test the proposed offer with an actual buying decision before committing to a wider launch.
These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.
Before we start
What to have ready before the work starts.
The records, access and decisions this work needs from temples. Anything missing is noted in the written scope, with who will supply it.
- The visitor book or darshan registration
- It shows where devotees come from and when. An old copy is enough. Without it, the map relies on staff memory alone, and that favours the loudest memories.
- A list of questions the office hears
- Ask the staff to write the questions they answer again and again. It need not be tidy. Without it we cannot find the gaps in the journey and may fix one that devotees do not notice.
- A trustee to approve the journey map
- One person must read the map and say whether it matches the temple's practice. If nobody does, the map reflects our assumptions and the messages written from it will be off.
- Examples of current messages sent
- Any confirmation slip, SMS or WhatsApp text the temple sends now. We improve these rather than replace them. If none exist, we write from scratch.
- Details of the festival crowd management
- Tell us how queues, tokens and special darshan are handled on a big day. The journey changes on those days. Without it, the map shows only an ordinary day.
How it works
How the buyer journey 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
Ask the counter staff how visits begin
We spend a session with the staff who greet devotees and take calls, and ask how people say they heard of the temple: a priest, a relative, a search, a festival notice. You supply any visitor-book entries. The answers give us the real starting points of a visit, not the ones we might guess.
- 2
Follow one family from home to darshan
We take a typical journey, for instance a family abroad wanting to book a seva for a parent, and write each step: searching, checking timings, finding the booking, paying, arriving, receiving prasadam. A trustee reads it and corrects anything that does not match practice. The result is a map with the temple's own words.
- 3
Mark where devotees stop or phone
We look at the points on that map where people give up or call the office: a payment that fails, a timing that conflicts, a seva they cannot find. The clerk tells us which calls come up again and again. These gaps are listed in order of how many devotees they affect, as the office sees it.
- 4
Write what each stage should say
For every stage we write the line a devotee needs: the confirmation message, the instructions for arrival, the thanks after a seva. The priests read anything about ritual. You decide the tone. What exists is a set of short messages and page texts placed along the journey.
- 5
Place the messages with the office
We put each text where the office can really send or show it, on the booking page, in a WhatsApp reply, on the board at the gate. The clerk tries sending them. If a stage depends on a person, we note who. The journey is then run by the office, not by us.
- 6
Compare the journey's gaps to the first list
The gaps we noted at the start, such as unanswered calls, failed payments and confused arrivals, are counted again after the changes have served a festival. We sit with the office registers and the call notes and report which gaps closed and which remain, and what that suggests for the next change.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales process design, at stage 1, prospecting and lead generation. 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.
Is this not the same as building a website?
Our devotees are mostly local. Is it still worth doing?
Who else is involved when a family chooses a seva or a donation?
A devotee started a booking and did not finish. How do we know why?
Does this change how devotees are treated at the temple?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
What do you need from us?
From the blog
Further reading for temples.
5 min read · 12 Oct 2026Tax receipts, FCRA and registrations: how an NGO should present credentials without overclaimingDonors look for registrations before they give. State what you hold in plain words, avoid implying more, and have your adviser confirm the wording.
5 min read · 14 Sept 2026Website for an NGO: the pages donors look for before they giveA first-time donor checks your website before paying. The pages and details they look for, in the order they look, and what a small NGO can leave out.
6 min read · 2 Jul 2026How an NGO builds a donor database it can actually useA donor database starts as one row per donor, a few columns and a named owner. The layout, the rules that keep it clean and when to move to a CRM.
More for temples
Related work to consider.
Closest to this: strategy and research
Also for temples
Or start from the overview: sales and marketing for temples.
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.