Skip to main content
GullySystem
Non-profit

Contact & Account Management for Temples

Keep organisations and their individual contacts connected.

CRM

Does this function belong in your operation?

Use when accounts have several contacts or owners change.

A business relationship or contact is added.

Devotees are found by phone number with gothra, nakshatra, rashi and family members, linked to every booking and donation they have made.

Bring the records the workflow depends on.

  • Account identifiers
  • Contact roles
  • Ownership rules

Outputs to check

  • Account and contact directory
  • Ownership and interaction history
  • Duplicate-review list

Follow the contact & account management workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Register the organisation

    Check identifiers and possible duplicates.

  2. 2. Add contacts

    Record each person's role and permitted communication details.

  3. 3. Assign ownership

    Identify who maintains the relationship and next actions.

  4. 4. Record interactions

    Keep history against the correct account and contact.

  5. 5. Maintain changes

    Handle moves, departures and mergers without transferring unrelated history.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Sales executive

Opens the account before a visit and sees the last order, the pending amount and the last complaint.

Accounts assistant

Finds the right person to call about a bill, and the tax ID that belongs on the invoice.

Owner

Reviews important account relationships, ownership changes and unresolved customer actions.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Duplicate account names

Compare identifiers before merging and preserve linked transactions.

Contact changes employer

End the former relationship without moving its history to the new account.

Account owner leaves

Reassign responsibility while retaining prior interaction authorship.

Can this work independently?

The directory can stand alone with controlled imports and updates. Leads, opportunities, billing and support use the same account identifier when connected. A person may have several business relationships, so contact identity should not be confused with one account's financial responsibility.

Systems and records it connects with

  • Lead management: Enquiry sources, owners and qualification decisions.
  • Quote and proposal management: Commercial proposal versions and acceptance details.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Accounting software: Posted financial entries and reconciliation references.

Configure, test and introduce the workflow.

  • Share your customer sheet or software. A summary lists the firms, people and branches found inside.
  • Decide which roles and terms matter in your trade. Try a trial account. It holds people, branches and terms. After a trial load your staff merge the flagged duplicates. The cleaned list returns for sign-off. Only then does the real load run.
  • Sales staff, accounts and the owner see their own part. Every role takes home a sheet. It is short and written for their work. Calls and visits are logged on the account from now on. The owner and team go through some accounts. Fields are adjusted as needed.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Contacts remain distinct from organisations.
  • Duplicates are flagged.
  • History survives reassignment.
Temples

How the business operates.

The temple office runs Temple Management Software, set up by GullySystem for trusts with a seva counter. Counter staff, priests and trustees use it. Seva and pooja bookings, donations by type, numbered PDF receipts, devotee details with gothra and nakshatra, festivals and priest duties sit together. The temple also gets a website with timings, sevas and a donation page.

Pooja booking

Set each seva’s price type, duration, days, time slots, bookings per slot and required devotee details. Bookings are numbered and move from pending to confirmed, assigned, completed or cancelled.

Online seva booking

Let devotees request a seva from your temple website with date, slot, gothra, nakshatra and sankalpa. The office confirms the request and takes payment at the counter when the family arrives.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Pooja booking. Set each seva’s price type, duration, days, time slots, bookings per slot and required devotee details. Bookings are numbered and move from pending to confirmed, assigned, completed or cancelled.
  • Online seva booking. Let devotees request a seva from your temple website with date, slot, gothra, nakshatra and sankalpa. The office confirms the request and takes payment at the counter when the family arrives.
  • Donations by type. Record every donation against a head you define, such as annadana, gau seva, building fund or hundi, with the donor’s tax ID, payment mode, reference and purpose. Each fund reads separately.
  • Online donations. Let devotees give from your website by bank transfer and enter the transaction reference. A numbered receipt is raised with that reference for matching against the bank statement.

Operational bottlenecks to check

Receipt books run out on festival days

On festival days a queue forms before the doors open. Receipts written by hand smudge in the heat of the counter, and the evening total may not match the cash box or the hundi count.

Bookings for the next day are not visible

Bookings arrive at the counter, by phone and through trustees, and each carries a different slip. The priest learns the sankalpa count only when names are read out at the homa.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Sevas and slots

    Enter each pooja or seva with the name your office uses, the amount or free-will offering, the days performed, time slots and bookings per slot. Choose which ones devotees may request online, and which stay counter-only.

  2. 2. Booking

    At the counter, staff pick the seva, date and slot, note the gothra, nakshatra, rashi and sankalpa, and take payment. Online requests arrive as pending bookings with those details filled in by the devotee.

  3. 3. Receipt

    Every paid booking or donation takes the next number in the series and comes out as a PDF. Donation receipts carry the trust’s tax-exemption details and the donor’s tax ID where the trust is registered for exemption.

  4. 4. Priest assignment

    The office assigns a priest to the booking and marks it confirmed, assigned or completed. The priest opens the day’s list with every sankalpa on it, in the order of the homa.

  5. 5. Closing the day

    The dashboard shows today’s donations, the month’s total, the day’s bookings and online requests still waiting, with collections by payment mode. Exports go to the trust’s accountant for the audit file.

Industry reports to connect with

  • Today’s and this month’s donations
  • Donations and seva bookings totals
  • Collections by payment mode: cash, cheque, bank transfer and online
  • Receipts register, downloadable as CSV

Questions before implementation.

When should temples consider contact & account management?

Use when accounts have several contacts or owners change. A business relationship or contact is added.

What should we bring to the requirements discussion?

Bring anonymised examples of Account identifiers; Contact roles; Ownership rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Keep organisations and their individual contacts connected. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Storage does not establish marketing consent or permission to share data.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Contacts remain distinct from organisations. Use this check when reviewing the first working version.

Talk to us

Discuss contact & account management for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements