Temples · Follow up systems
Answer the mantapa enquiry that arrived on Saturday night.
A follow-up routine for a temple decides what happens to the enquiry nobody replied to: the family asking whether the mantapa is free on a muhurtham date, the sponsor who pledged and never sent the amount, the seva booking whose payment did not go through. GullySales sets who replies, and when.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What follow up systems means
A follow-up system is the set routine for calling, messaging or emailing an enquiry more than once, since most buyers do not decide on the first conversation. GullySales sets the number and timing of follow-ups so an undecided buyer keeps hearing from you until they decide either way.
Last updated 14 Nov 2026.
For temples
Where it usually goes wrong, and what we would do.
“A muhurtham date will not wait for the office to open”
A family fixing a wedding is asking three venues at once. The temple that replies while the date is still free takes the booking, and the trust never learns what the silence cost.
“A pledge made at a festival needs a reminder, not a chase”
Somebody who announced a sponsorship during an utsavam meant it. A short, respectful message with the purpose and the account details is the only thing that was missing.
“A failed payment is a devotee who tried”
A seva booking that ended in a failed transaction is not a lost devotee. Somebody has to notice and write back, or the family concludes the temple did not want the offering.
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.
A named person reading the enquiry inbox
One person at the office who goes through enquiries at a fixed hour, with an automatic message telling a devotee when the office is open.
Result: An enquiry is acknowledged even when it arrives at night.
A routine for hall and accommodation enquiries
A fixed way of checking the date, replying with availability and holding it while the family decides.
Result: A family fixing a muhurtham hears back while the date is open.
A follow-up on pledges made at an event
A respectful message carrying the purpose, the amount pledged and how to send it, recorded against the family who pledged.
Result: A pledge becomes a receipt rather than a memory.
A check on incomplete bookings and payments
A daily look at seva bookings where the payment did not go through, and a short message offering to help complete it.
Result: A devotee who tried to give is helped instead of ignored.
A written point at which the office stops
How many reminders a pledge or an enquiry receives, and the wording of the last one, agreed by the committee.
Result: Nobody at the temple is left wondering whether to write again.
A confirmation before the seva date
A message to the family ahead of the day, with the time to arrive, the gotra recorded and what they should bring.
Result: Families arrive prepared and the counter queue moves.
How the result is measured
- Follow-up completion rate
- Average number of follow-ups before close
- Enquiries closed after repeat follow-up
Recorded as a baseline before work starts, so every later report has an honest comparison.
Follow-up routine for temples
Every devotee query, hall booking and pledge is logged with a person to reply and a respectful way to remind.
- Seva booking, payment failed
- The office rings the devotee, explains the failure and sends the payment link again. Record the seva, the date and the name for the sankalpa.
- Mantapa enquiry for a muhurtham
- Reply with availability, the booking terms and a way to hold the date, then ask for the family's decision. Record the date and the contact for the booking.
- Pledge made at a festival
- The treasurer sends a short, respectful message with the purpose and the account details. Record the pledged purpose and thank the donor on receipt.
- Annadanam or sponsorship enquiry
- Ask the date, the number of devotees and the menu, then confirm with the kitchen head. Write the sponsor's name only as they have asked.
- NRI devotee asks about online darshan or seva
- Reply with the time zone, the booking page and the way to receive the prasad. Record the address and the date of dispatch.
- Accommodation or guest room request
- Confirm availability and rules, including check-in times and any dress code. Record the arrival date and the number of guests.
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.
- Enquiries come in on several personal phones and nobody gathers them, so there is no single list to follow up.
- No one in the office is named to reply on the weekend of a festival, when the bookings arrive.
- You intend to chase pledges from devotees who have not asked to be contacted again.
Before you decide
Agree the work. Know how to judge it.
Follow-up systems for temples: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
Trace recent enquiries from arrival to the last recorded action. Include a won enquiry, an unsuitable one, and one that went quiet, with personal details removed for the initial discussion.
Make the scope clear
Agree who accepts each enquiry, what makes it qualified, and how ownership changes. Include a rule for missed replies and a clear reason for closing an enquiry.
Check the work in use
Pick an enquiry at random and ask the team to find its owner, latest conversation, and next action. Check that the record agrees with what actually happened.
Know when to change course
If no one has capacity to respond, assign that responsibility before buying more leads. Automation can support the owner, but it cannot replace an unresolved handover.
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 message book and booking ledger
- These show who asked and who was answered. Photographs of the pages are enough. Without them we cannot find the enquiries that were left, and the system starts with no history.
- A clear owner for each type of query
- The trust must name who answers receipts, bookings and complaints. A single page works. If the names are vague, reminders reach a desk where nobody acts on them.
- Consent wording for contacting devotees
- The trust must settle what a devotee is told when giving a phone number. Your adviser confirms the wording. Without it, we send nothing beyond a direct reply to a message the devotee started.
- Approved templates in the temple's languages
- A priest or trustee reads each message in every language used. A mistranslated term causes offence. Missing approval means messages go out in one language only.
How it works
How the follow up systems 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
Sort the enquiries lying in the registers
We take the phone message book, the booking ledger and the WhatsApp chats and separate the enquiries that were answered from those left hanging: a family who asked about a seva date and heard nothing back, a donor who asked for a receipt. You tell us which kinds the trust cares about first. The result is a list of people who are still waiting.
- 2
Decide who answers what at the office
We write down who handles seva questions, who sends receipts and who speaks to donors. The priests take only ritual questions. A trustee signs this one-page allocation. If the roles overlap, we settle them before any reminder is set up, so a devotee does not get two replies or none.
- 3
Write the follow-up messages
We draft the reply to a booking, the receipt message, the reminder before a seva date and the note of thanks after the festival. A priest reads anything about the ritual. You decide the greeting and the language. The drafts are short and read as the temple speaking, with no promise of blessings.
- 4
Set the reminders against the temple calendar
We attach each message to a trigger the office already knows: a booking made, a seva date approaching, a festival ending. The clerk sees how a reminder will appear in the list and marks it done. Nothing is sent to anyone who has not agreed to be contacted.
- 5
Compare answered enquiries to the starting list
The count of waiting enquiries we found at the start is set beside the office's records after a festival. We report how many were answered, how many bookings followed and which messages devotees replied to. Anything that did not work is changed before the next utsavam.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales process design, at stage 2, qualification. 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.
We are a small trust with one person in the office. Is this realistic?
Is it appropriate to remind somebody about a pledge?
How should the temple office reply to a devotee who complains?
What if the same devotee keeps asking for a booking we cannot give?
What if a devotee does not want reminders?
Who sends the messages, the temple or GullySales?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
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: leads and follow-up
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.