Skip to content
GullySales

Every customer message lands in one place, with an owner and a clock.

Gully Sales builds the desk that answers your customers: phone, WhatsApp, email and web enquiries pulled into one queue, with routing, response times, shifts and reporting your own team can run.

  • One queue for phone, WhatsApp, email and web, so nothing sits unanswered.
  • Response and resolution times written down, then enforced by the system itself.
  • A roster, a routing rule and a named owner for every request that arrives.
Book a free auditTalk to us

Gully Sales Private Limited works with small and medium businesses across India, and builds the desk to run on the people and tools you already have.

In one paragraph

What is Helpdesk and Contact Centre Setup?

Helpdesk and contact centre setup is the work of building the desk that answers your customers. Gully Sales brings phone, WhatsApp, email and web enquiries into one queue, configures the ticketing and telephony, sets routing, response clocks and shifts, trains the people who reply, and hands you the weekly reporting.

The problem

Your customers reach you in five places, and no one place holds the list.

Ask your team one question: how many customers are waiting for an answer right now, and which of them has waited longest? In most growing businesses nobody can say. The call log sits on a handset, the messages on somebody's phone, the enquiries in a mailbox, and none of those is a list. Work is remembered rather than tracked, so a request gets closed when somebody happens to think of it, and forgotten when nobody does.

You will recognise it as

  • A customer says they have already asked twice, and nobody in your team can find either message.
  • Requests live inside personal WhatsApp accounts and mailboxes, so a colleague on leave takes the history away with them.
  • You cannot say how many requests came in last month, or how long an average one took to close.
  • The same question is answered differently by two people, and both answers sound reasonable.
  • Escalations reach a director or the owner because there is no other route upward.
  • Evenings, Sundays and festival days have no cover, so Monday starts with a backlog nobody owns.

What it costs the business

  • Customers repeat themselves, and each repetition costs more goodwill than the original problem did.
  • Senior people spend their day chasing routine requests, because they are the only reliable route to an answer.
  • Renewals and repeat orders quietly move elsewhere, and the reason never appears in any report you read.
  • Replacing a support person becomes painful, because the knowledge sits in one head rather than in a system.

Why it persists. It persists because every individual channel appears to be working. The phone rings and somebody picks it up. The WhatsApp message gets a reply, eventually. Nothing is visibly broken, so nothing gets fixed. A ticketing tool looks like an expense with no obvious return, and the people who would configure it are the same people answering the messages all day. So the desk stays informal, and its real cost shows up as churn, escalations and senior time rather than as a line anyone can point to.

If it stays unresolved. Left alone, the load rises with the customer count and the setup does not. Response times stretch, the same complaints repeat, and your strongest people spend the week on requests a trained coordinator could close. Customers stop reporting small problems and start leaving quietly instead, which is the most expensive kind of feedback because it never reaches you at all.

What changes

Every request has a place, an owner and a time it is due.

In the first weeks

  • Every channel your customers use arrives in one queue that any authorised person can open.
  • Each request carries an owner, a category and a due time from the moment it is created.

In how the work runs

  • Routing rules send a request to the right person or team without anyone forwarding it by hand.
  • Shifts and leave cover are rostered against your real arrival pattern, including evenings and Sundays.
  • Agents answer from approved templates and a knowledge base, so the same question gets the same answer.

In sales and marketing

  • Senior people stop being the escalation route of last resort and return to work only they can do.
  • Customers who would have left silently now have a channel that visibly responds, which supports renewal.

In what management can see

  • Volume, response time, resolution time, backlog and reopened requests sit on one weekly report.
  • Reason codes show which product, process or customer group is generating your support load.

Over the longer term

  • Support becomes a function the business owns, so a resignation no longer takes the history with it.
  • The desk gives your product and operations teams a factual list of what keeps going wrong.

We control the design, the configuration, the documentation, the training and the reporting. Whether resolution times and retention improve also depends on staffing, product quality and the decisions your team takes on the desk, so we report what is measured rather than promise a number.

Who it is for

This suits businesses whose customers now outnumber the people answering them.

The businesses it suits

  • Service, subscription and annual-contract businesses where renewal depends on how support felt last quarter.
  • Companies whose enquiries and complaints arrive across phone, WhatsApp, email, web forms and social messages.
  • Businesses running a support team of roughly three to thirty people with no ticketing system behind them.
  • Dealer, distributor and franchise networks needing one route for partner queries instead of many personal numbers.
  • Healthcare, education and hospitality operators handling appointment, billing and service requests all day.
  • Firms that already bought a helpdesk tool but barely configured it, so the team still works in WhatsApp.

What usually prompts the call

  • A complaint reached the owner because nobody could say who was handling it.
  • You are hiring more support people and cannot describe what each one is supposed to do.
  • A customer left, and the exit reason turned out to be a request that was never closed.
  • You have crossed the point where one person can hold every open issue in their head.
  • A client, auditor or tender has asked for service levels and handling records you do not have.
  • You are opening a second location or a new product line and support has to cover both.

What Gully Sales does

The work, component by component.

Your service promise, written down

We write what your business commits to: the hours the desk is open, the channels it answers, how quickly a customer hears back on each, what counts as resolved, and what happens when the promise cannot be kept. It is set against your real staffing and your customers' expectations rather than copied from a larger company, so your team can keep it on an ordinary Tuesday, not only on a good one.

Why it matters:
A team without a written promise invents one request at a time, and customers end up judging you against whatever the last person happened to tell them.
You receive:
Written service promise covering hours, channels, response and resolution commitments, and the stated exceptions.
Business value:
Everyone answering knows what they owe the customer, and you can publish the promise without fearing it will be missed.

Channels consolidated into one queue

We map where your customers actually reach you today, including the numbers and mailboxes nobody officially owns, then decide which channels stay, which merge and which close. Phone, WhatsApp Business, email, web forms and social messages are routed into one queue, so a request exists in exactly one place with one history whichever door it arrived through.

Why it matters:
Multiple channels are not the problem. Multiple lists are. One queue is what lets somebody answer without first checking with three colleagues.
You receive:
Channel map with a keep, merge or close decision for each, and the routing that lands every channel in one queue.
Business value:
A customer can write on WhatsApp on Monday and telephone on Thursday, and your team still sees one conversation.

Queue discipline and the daily routine

We set how the queue is worked each day: the morning triage that assigns everything unassigned, the rule that no request sits without an owner, how ageing items surface before they breach, what one shift hands to the next, and how a backlog is cleared rather than carried forward. This is the routine that makes the day predictable for the people on the desk.

Why it matters:
A tool full of tickets that nobody is required to look at is only a slower version of a WhatsApp group.
You receive:
Daily and weekly desk routine covering triage, assignment, ageing checks, shift handover and backlog clearance.
Business value:
Nothing sits unowned overnight, and whoever starts a shift knows exactly what they have inherited.

Roles, roster and cover

We define the roles your desk needs at its size: who answers first, who takes the harder cases, who owns the queue as a whole, and who is called when something must go beyond the desk. Then we roster against your real arrival pattern, hour by hour and day by day, including evenings, Sundays and festivals where your customers write then. Where a role does not exist, we write it.

Why it matters:
Most desks are staffed by habit rather than by arrival pattern, so they are crowded when it is quiet and empty when the calls come.
You receive:
Role definitions, a shift roster built on measured arrival volumes, and leave and absence cover rules.
Business value:
Cover matches demand, and nobody has to guess who is responsible when a difficult request arrives at six in the evening.

Service levels the system enforces

We agree response and resolution targets by priority and by channel, then configure them as timers inside the tool so the clock runs whether or not anyone remembers it. Warnings appear before a deadline rather than after it, and the rules for pausing a clock, such as waiting on the customer or on a supplier, are written down so the reported numbers stay honest.

Why it matters:
A service level that lives in a document is a wish. One that lives in the system changes what people actually do at four in the afternoon.
You receive:
Priority matrix, response and resolution targets, timer configuration and the written pause and breach rules.
Business value:
You can commit to service levels in front of a customer or a tender, and show month by month whether they were met.

Technology chosen for your size

We select and configure what the desk needs: ticketing, the WhatsApp Business platform where it fits, a shared mailbox or cloud telephony with an IVR menu and call recording, and the link to whatever CRM you use. Selection follows your volume, your channels and your team's comfort. Whatever you already pay for is configured first, before anything new is recommended.

Why it matters:
Tools are usually bought before the work is understood, which is why so many licences sit unused beside the WhatsApp group carrying the real load.
You receive:
Tool selection note, configured ticketing and telephony, channel integrations, user roles and permissions.
Business value:
You run on a system sized for your business rather than on a platform designed for a company ten times larger.

Quality checks and the insight loop

We set up a light quality review: a sample of calls and written replies scored each week against an agreed sheet, coaching notes for the people reviewed, and a satisfaction question asked after closure. The recurring reasons behind requests are tagged and taken monthly to the teams who can remove them, so the desk reduces its own load instead of only absorbing it.

Why it matters:
Without review, quality drifts to whatever the busiest person has time for, and nobody outside the desk ever learns why customers keep writing in.
You receive:
Quality scoring sheet, weekly review routine, the post-closure satisfaction question and a monthly reason-code report.
Business value:
Replies stay consistent as the team grows, and repeated causes reach the people who can actually remove them.

What you will have at the end.

  • Written service promise stating hours, channels, response and resolution commitments, and the exceptions.
  • Channel map of every number, mailbox and account customers use, with a keep, merge or close decision for each.
  • One configured queue receiving phone, WhatsApp, email, web form and social messages with a single customer history.
  • Priority matrix with response and resolution targets by priority and channel, configured as timers in the tool.
  • Daily desk routine covering triage, assignment, ageing checks, shift handover and backlog clearance.
  • Role definitions with a shift roster built on your hour-by-hour arrival pattern, plus leave and absence cover rules.
  • Configured ticketing and telephony, including the IVR menu, call recording, user roles, permissions and CRM links.
  • Reply templates and an agent knowledge base for your most frequent requests, with a sample you can read first.
  • Escalation path naming who is contacted, at what point, and with what information attached.
  • Quality scoring sheet with one anonymised sample review, and the weekly coaching routine around it.
  • Weekly and monthly report formats showing volume, response and resolution times, backlog, reopens and reason codes.
  • Ninety-day roadmap with the go-live sequence, review dates and the baseline numbers agreed at the start.

How it runs

The engagement, step by step.

  1. 1

    Read how requests reach you today

    We sit with the people who answer customers, list every number, mailbox, form and account in use, and read a month of recent requests. We look at when they arrive, what they are about, who answered, how long each took and which ones came back. Where records do not exist we say so plainly, and count from the first clean week rather than reconstructing numbers nobody can verify.

    You provide:
    Time with the people who answer customers, access to existing mailboxes and chat histories, and any records you already keep.
    We produce:
    A written picture of current volume, channels, arrival pattern, waiting times and the recurring reasons behind requests.
    Done when:
    You and we agree what the desk is carrying today, and where requests are being lost.
  2. 2

    Agree the service promise and priorities

    We set what your business will commit to, by channel and by priority, against staffing you will genuinely fund rather than against an aspiration. That covers operating hours, first-response and resolution targets, what counts as urgent, what counts as resolved, and how a promise that cannot be kept is communicated. Whoever owns the customer relationship signs it off.

    You provide:
    A decision on operating hours and staffing budget, and sign-off from whoever owns the customer relationship.
    We produce:
    The written service promise and the priority matrix, with the pause and breach rules stated.
    Done when:
    The promise is signed off and can be stated to a customer without hesitation.
  3. 3

    Design the desk and configure the tools

    We define the roles, the roster and the routing, then select and configure the ticketing, telephony and channel integrations that suit your volume and your team. Whatever you already own is set up first. Everything is built where your team can try it before a single customer touches it, and the fields are kept few enough that an agent will actually fill them.

    You provide:
    Administrator access to existing tools, a decision on any new licences, and two or three people to test the setup.
    We produce:
    A configured helpdesk with queues, routing, timers, roles and permissions, plus the roster and role definitions.
    Done when:
    Your team can raise, route, answer and close a test request end to end without asking us how.
  4. 4

    Write what the team will say

    We build the reply templates, call openings, holding messages and knowledge base entries for the requests that arrive most often, in the languages your customers use. Your team reviews and corrects the wording, because it is their voice the customer hears. We also write what must never be committed to on a call, so nobody promises a refund or a date that your business cannot keep.

    You provide:
    Product and policy boundaries, what may and may not be promised to a customer, and one review session.
    We produce:
    Approved templates, call guides and knowledge base entries for your most frequent request types.
    Done when:
    You have approved the words that will be sent and spoken in your company's name.
  5. 5

    Train the team and run a pilot

    We train the people on the desk on both the tool and the routine, then run a pilot across a limited set of channels or customers. Early days expose which priority is set too tightly, which routing rule sends work to the wrong person and which template does not survive a real customer. The setup is corrected on that evidence before the rest goes live.

    You provide:
    The team's time for training, and a named person who can take decisions quickly during the pilot.
    We produce:
    Trained agents, a pilot report, and the corrections made to routing, priorities and templates.
    Done when:
    Requests flow through the desk correctly for an agreed period without anyone rescuing them manually.
  6. 6

    Go live channel by channel

    Channels are switched over in a planned order rather than all at once, so trouble in one does not disturb the others. Old numbers and mailboxes are redirected instead of abandoned, customers are told where to write, and somebody watches the queue closely through the first weeks. We stay available across the transition and log every issue raised until it is closed.

    You provide:
    Approval of the switchover order, and a customer communication your team is willing to send.
    We produce:
    A live desk with every agreed channel routed in, and a switchover log with issues raised and closed.
    Done when:
    Every agreed channel arrives in the queue and no customer route is left unwatched.
  7. 7

    Report, review and settle the routine

    Weekly and monthly reporting begins and we sit in the review with your team: what came in, what was answered on time, what is ageing, what came back and why. Quality reviews start on a small sample. Decisions are written down so the routine improves steadily instead of being argued again next month, and the reason codes start reaching the teams who can act on them.

    You provide:
    An hour a week from whoever owns the desk, and a decision-maker for anything that must change.
    We produce:
    Weekly reports against the agreed baseline, quality review notes, and the revisions made to the routine.
    Done when:
    Your team runs the weekly review without us, using the same report each time.
  8. 8

    Hand over and step back

    We hand across the documentation, the tool administration and the training material, and coach the person who will own the desk after us. Then we step back on an agreed date, with a review some weeks later to see what has drifted, what the team has changed sensibly and what needs correcting before it becomes habit.

    You provide:
    A named owner for the desk who can take on administration, rostering and the weekly reporting.
    We produce:
    Complete documentation, administrator handover, training material and a post-handover review.
    Done when:
    The desk runs on your people and your tools, with us in reserve rather than in charge.

Ways to work with us

Start with an assessment, a full build, or help running what you already own.

Customer contact assessment

A short engagement that reads a month of requests across every channel, measures what actually happens to them, and returns the service promise, the priority matrix and the two or three changes worth making first.

Helpdesk setup

The full build for a business running on mailboxes and WhatsApp: channels consolidated, ticketing configured, roles and roster defined, templates written, the team trained and the reporting handed across.

Contact centre build

For higher volumes and voice-led operations: telephony and IVR, queue and routing design, shift planning against arrival patterns, call quality review, and the daily reporting a support manager needs.

Rescue an existing tool

You bought a helpdesk and the team still works in WhatsApp. We configure what you own around how your business really operates, retrain the team, and move the actual work into the system.

Ongoing desk management and coaching

We run the review rhythm, score quality, coach your agents and maintain the reporting for an agreed period, then hand back to a manager we have trained to keep it going.

Why Gully Sales

What you are actually choosing when you choose us.

We size the desk for your business, not for a call centre.

A team of four does not need what a team of forty needs. We design against your arrival pattern and your budget, and we will say plainly when a shared mailbox and a written routine are enough for the year ahead.

The setup is built around how Indian customers actually reach you.

WhatsApp carries more of your customer conversation than any web form does. We treat it as a first-class channel with an owner and a clock, alongside calls answered in the language your customer prefers.

Your team has to be able to run it after we leave.

Everything is documented, the administration is handed over, and we coach the person who will own the desk. A setup that needs us every week is a setup that has not worked.

We configure what you already own before selling you anything.

Most businesses we meet already pay for tools they never set up properly. We start there. New licences are recommended only where the volume, the channels or the shift pattern genuinely need them.

The desk is treated as part of your revenue system.

Gully Sales works across marketing, sales, customer success and revenue operations, so what customers report on the desk reaches the people running the product, the process and the accounts.

We report the numbers as they are.

Volume, response and resolution times, backlog, reopens and satisfaction are reported against a baseline recorded before we started, including the weeks that read worse than anyone hoped.

Where it applies

The same service, in different businesses.

Healthcare and diagnostics

The situation:
A multi-branch clinic takes appointment, report and billing queries on four mobile numbers, and patients who cannot get through simply call a doctor's personal line instead.
How it applies:
Numbers are consolidated behind one line with an IVR and a shared queue, request types are separated, and evening cover is rostered against actual call arrival.
Likely benefit:
Patients reach the clinic on the first attempt, and clinicians stop acting as the switchboard for routine queries.

Software and subscription services

The situation:
Support runs on a shared mailbox, so nobody can tell which client is waiting, for how long, or whether the same fault has been reported before.
How it applies:
Tickets are raised per client with priority timers, routing separates account questions from technical faults, and reason codes go to the product team monthly.
Likely benefit:
Renewal conversations start from a record of how the year was actually handled, rather than from competing memories.

Manufacturing and industrial equipment

The situation:
Service complaints reach three plant engineers directly by phone, and a machine down at a customer site is escalated only when that customer calls the owner.
How it applies:
One service desk logs every breakdown with priority and location, dispatches to the nearest engineer, and holds the service history of each installed machine.
Likely benefit:
Breakdowns are attended in a defined order, and the machine's history is available before the engineer travels.

Education and training

The situation:
An institute handles admission, fee and timetable queries across WhatsApp, phone and Instagram, with an admission-season peak nobody has ever staffed for.
How it applies:
Channels merge into one queue, seasonal cover is rostered against last year's arrival pattern, and repeat questions are answered from a maintained knowledge base.
Likely benefit:
Admission season is staffed on evidence, and parents receive consistent answers whichever channel they choose.

Dealer and distributor networks

The situation:
Dealers send stock, warranty and claim requests to individual sales managers, so a manager on leave stops that dealer's business for a week.
How it applies:
One partner desk receives every dealer request, routes by request type rather than by relationship, and holds the claim history in one place.
Likely benefit:
Dealers get an answer regardless of who is travelling, and claim delays become visible rather than anecdotal.

E-commerce and direct-to-consumer brands

The situation:
Order, return and refund messages arrive on Instagram, WhatsApp and email, and the same customer is answered twice with different information.
How it applies:
All three channels feed one queue linked to the order record, with templates for common return and refund questions and one owner per conversation.
Likely benefit:
A customer receives one answer, and refund delays surface as a pattern rather than as individual angry messages.

Proof

Work we can point to.

Vijaya Hospital

The problem:
Patient enquiries were growing while the way those enquiries and daily operations were handled needed strengthening.
What we did:
Gully Sales worked on the hospital's digital presence, patient enquiries and operational efficiency.
Over:
The result:
The case study reports a strengthened digital presence, increased patient enquiries and improved operational efficiency.
Read the case study

Premier Marketing

The problem:
Enquiries arrived from domestic and industrial buyers, but handling each one consistently was difficult.
What we did:
Gully Sales worked on reach, lead handling and sales acceleration across the domestic and industrial sectors.
Over:
The result:
The case study reports enhanced reach, streamlined lead handling and accelerated sales.
Read the case study

Natural Gases

The problem:
Visibility and sales operations needed better workflows to keep pace with demand for industrial and medical gases.
What we did:
Gully Sales worked on visibility, sales operations and demand generation supported by smarter workflows.
Over:
The result:
The case study describes improved visibility, stronger sales operations and growing demand through smarter workflows.
Read the case study

Questions buyers ask

Before you enquire, the answers you will want.

What service standards matter most to our customers?

Three, in this order. First, that somebody acknowledges them quickly, because silence is what turns a query into a complaint. Second, that they are not asked to repeat themselves, which is why one queue and one history matter more than raw speed. Third, that the answer holds: a request closed and then reopened costs more trust than one that took a day longer. Resolution time matters, but it matters less than these three.

How long does a helpdesk or contact centre setup take?

It depends on how many channels are being consolidated and whether voice is involved. The reading and the service promise come together quickly. Configuration, templates and training take longer, and we always pilot before full go-live, because the early days expose routing and priority errors no design session will. We agree the sequence and checkpoints in writing before starting, and we do not commit to dates that depend on decisions your team has yet to take.

What do you need from us to begin?

Time with the people who answer customers today, access to the mailboxes, numbers and chat accounts in use, and whatever records you keep. Then a decision on operating hours and staffing, sign-off on the service promise from whoever owns the customer relationship, administrator access to any tools you already pay for, and a named person who will own the desk after we step back. That last one matters most of all.

How is the success of the desk measured?

Against the baseline recorded before configuration began. We report volume by channel, first response and resolution time against the promise, backlog and ageing, first contact resolution, reopened requests, escalations and satisfaction. Over a longer period we add renewal, churn and expansion among customers who contacted the desk. The first month is read on leading signs only, because retention effects need a full renewal cycle before they say anything reliable.

What is excluded from the scope of this work?

We do not employ or supply your agents, and we do not answer your customers for you under this engagement. We do not fix the product or process faults that generate the requests, although we will report them clearly. Software licences, telephony charges and messaging platform fees are paid by you directly to the provider. Retention campaigns, loyalty programmes and compensation policy are separate pieces of work.

How is this different from designing our support process?

Process design decides how a single request should be handled from arrival to closure. This work builds and staffs the desk that does the handling: which channels arrive where, which tool holds the queue, who sits on which shift, what the timers enforce, and what the reports show each week. The two fit together. If your process is written already and simply has nowhere to live, this is the missing piece.

Do we need to buy a helpdesk tool?

Not necessarily, and not first. We look at your volume, channels and team before recommending anything, and we configure what you already own before suggesting a purchase. A small desk can run well on a shared inbox tool with clear rules. Once volume, several channels or shift work arrive, a ticketing system earns its cost in requests that no longer go missing. We will tell you which side of that line you sit on.

Can WhatsApp be part of a proper helpdesk?

Yes, and for most Indian businesses it has to be, because that is where customers already are. Through the WhatsApp Business platform, messages arrive in the same queue as email and calls, carry an owner and a timer, and keep a history against the customer record. What changes is that conversations stop living on somebody's personal phone, so a colleague on leave no longer takes the thread away with them.

4 more questions

How many people do we need on the desk?

That comes from your arrival pattern, not from a ratio. We count how many requests arrive by hour and by day, how long each type takes to handle, and what your promise commits you to, then roster against that. Often the finding is not that you need more people, but that the ones you have are covering the wrong hours. Where more are genuinely needed, we write the role description before you hire.

Will our support team resist a ticketing system?

Some resistance is normal and usually fair, because a badly configured tool adds clicks without helping anyone. We reduce it by keeping the fields few, building the routine with the team rather than for them, training on their own real cases, and piloting before switching everything over. Agents accept a system that shows them what is theirs and protects them from being blamed for work nobody ever assigned.

Can you set up service levels we can commit to in a tender?

Yes, provided they are set against staffing you will actually fund. We write response and resolution targets by priority and channel, configure them as timers, and define when a clock pauses, so the reported numbers hold up under scrutiny. You then have a documented service promise and a monthly record of performance against it, which is what a corporate customer, an auditor or a tender committee wants to see.

What happens after handover?

The documentation, the tool administration and the training material are yours, and we coach the person who will own the desk before stepping back on an agreed date. Many clients keep us for a monthly review through the first quarter, when the reports start raising questions about the product and the process rather than about the desk itself. Others take it in-house immediately. Both work.

Talk to us

Find out what your customers are actually experiencing.

Request a Customer Growth Assessment and we will look at how requests reach your business today, what happens to them, and where customers are quietly being lost. It is a working conversation, not a pitch.

  • No obligation and no sales script
  • A reply from someone who does the work
  • Your details are never sold or shared

Your details are used only to reply to your enquiry. We do not sell or share them, anything you tell us about your customers and complaints stays confidential, and we can sign a confidentiality agreement first.

Protected by reCAPTCHA — Google’s privacy policy and terms apply.

Get a free audit of how you sell, and a scored report of where the work is.

Book a free audit
Book a free audit