Skip to content
GullySales

Mobile phone stores · Lead routing and assignment

When an enquiry arrives, one named person is responsible for the next reply.

Lead routing and assignment sets the rules for which salesperson, branch or specialist receives each new enquiry, including what happens when information is missing or someone is away. GullySales documents those decisions, configures assignment where your systems support it, and sets up a manual handoff where automation is not available.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

Mobile Phones & Accessories product collection

Start with the buying decision

Which record or handover breaks between the enquiry and its outcome?

Industry membership alone does not establish fit. The service exclusions, your operating model, and the records available determine the scope after your requirements brief.

Your team approves the scope and any commitments to buyers. GullySales does not assume authority over pricing, staffing, or delivery promises unless a specific responsibility is agreed in writing.

The context for Mobile phone stores

Start with the decisions in your own enquiry records.

Trace a real enquiry across the people and systems involved. Record missing information, duplicate work, and the decision that is still waiting for an owner.

How people choose in this industry

Customers choose a mobile store on price, on stock and on trust. They want the handset today, they want to know the exchange value of the old phone before they travel, and they want to hear that no-cost EMI really costs nothing extra. A shop that gives a straight answer on all three, in the customer's language, can win against a bigger name that answers slowly.

After the sale, the shop is judged on small things. Was the screen guard fitted, was data moved across, did someone answer when the phone hung a week later? Families send the next phone buyer to the shop that did these quietly.

The decision before implementation

Define the process and access permissions before changing software settings or adding automation.

Existing industry priorities to review

  • Reply to price and stock enquiries on WhatsApp quickly and accurately
  • Honest exchange value quoted before the customer visits
  • EMI and finance options explained in plain words
  • Launch-day enquiry capture and follow-up calls
  • Google Business Profile with current stock photos and timings

These describe the industry's wider priorities. The written scope identifies which this service will address.

Industry application review

Test the service against a problem in your own records.

These review scenarios connect the industry context to a possible output and a checkable next step. They are scope questions, not client results or a promise that every industry problem belongs in this engagement.

People ask the price on WhatsApp and never come in

The reply goes out hours later, or it is a number with no stock note, and the customer has already messaged three other shops.

Confirm the scope first

Check whether this issue belongs in the lead routing and assignment engagement or requires different work. The industry problem alone does not establish that this service will solve it.

What to bring

Bring the original enquiry record, its changes, the people involved, and any handover that required rework.

Proposed completion check

Record the scope decision and its reason. If the issue is outside this engagement, identify the responsible team or the separate work required.

Launch days bring crowds that we cannot follow up

Twenty people ask about a new model, the staff note a few numbers on paper, and most of those enquiries are never called back.

Confirm the scope first

Check whether this issue belongs in the lead routing and assignment engagement or requires different work. The industry problem alone does not establish that this service will solve it.

What to bring

Bring the original enquiry record, its changes, the people involved, and any handover that required rework.

Proposed completion check

Record the scope decision and its reason. If the issue is outside this engagement, identify the responsible team or the separate work required.

The problem

What lead routing and assignment is meant to address.

  • “The buyer keeps getting transferred”

    A product enquiry reaches a salesperson who cannot answer it. Forwarding the message does not establish who must reply, so the buyer waits while your team sorts out responsibility.

  • “The quickest person gets all the enquiries”

    A shared inbox rewards whoever notices a message first. Territory coverage and available capacity have little say in who receives the work.

  • “Two salespeople claim the same enquiry”

    A buyer's location points to one branch, while the product points to a specialist elsewhere. Without a priority rule, both people pursue it or each waits for the other.

  • “Nobody covers the person on leave”

    New enquiries continue going to an unavailable salesperson, while their existing enquiries sit untouched. A backup needs authority to take over, not just access to the inbox.

Who it is for

Check your operating model against the scope.

  • Manufacturers and dealers dividing B2B enquiries by territory or product range
  • Multi-branch businesses sending enquiries to the location responsible for serving the buyer
  • Sales teams sharing IndiaMART, JustDial, website, or Meta enquiries
  • Companies with specialists handling technical enquiries or larger purchase requirements
  • Hospitals and hotels with separate desks for different enquiry types

Before you decide

When this may not be the right fit.

  • You personally answer every enquiry and have nobody else to assign it to.
  • Your manager handles a small enquiry volume reliably, without missed handoffs or ownership disputes.
  • You need more enquiries rather than better assignment of the enquiries already arriving.

Choose the right scope

Start with the work your business needs.

  1. Branch and territory routing

    For enquiries that belong to a specific service area or branch. We apply your approved coverage map to assignment; redesigning the territories themselves is separate territory-planning work.

  2. Product and specialist routing

    For manufacturers or dealers whose enquiries need different technical knowledge. The rules decide when a product specialist owns the enquiry and when the territory salesperson remains responsible.

  3. Shared enquiry rotation

    For teams receiving enquiries through a common inbox or marketplace account. Eligible salespeople receive assignments through an agreed rotation, with a manual version where the tool cannot support it.

  4. Leave and exception coverage

    For teams with workable everyday assignment but poor backup arrangements. The scope concentrates on unavailable owners, unmatched enquiries, and the manager's decision when an enquiry remains untouched.

What we do

Agree the outputs before work begins.

These are the lead routing and assignment deliverables available for mobile phone stores. Your written scope identifies the included work and responsibilities.

  1. Routing rules document

    A written assignment table covering the agreed criteria, such as territory, product, language, or deal size. You check examples against it and approve which rule wins when criteria overlap.

  2. Intake field specification

    A list of the information each source must provide for routing, including city, pincode, or product interest where needed. Your team checks sample incoming records for missing fields before those fields drive assignment.

  3. Assignment configuration

    Rules configured in your CRM or receiving tool where supported, with a documented manual alternative where needed. Test enquiries show the assigned owner and expose any unsupported part of the proposed workflow.

  4. Fallback and reassignment rules

    Named backups, a catch-all owner, and agreed conditions for moving an untouched enquiry. You check what happens when a field is blank, nobody matches, or the original owner is unavailable.

  5. Rotation and capacity settings

    An agreed rotation among eligible salespeople, with workload limits and leave handling where your tool supports them. Your sales lead checks that eligibility takes priority over simply sharing enquiry counts equally.

  6. Manager assignment view

    A CRM view or shared record showing ownership, unassigned enquiries, and items past the agreed waiting limit. The manager can inspect individual records rather than relying on a total that hides missed handoffs.

  7. Assignment handover notes

    Instructions for updating availability, handling exceptions, and approving changes to the rules. Your nominated manager walks through these actions before taking responsibility for the live process.

How the result is measured

  • Correct assignments checked against approved rules
  • Time from enquiry arrival to assignment, measured separately from first reply
  • Unassigned or untouched enquiries beyond the agreed limit
  • Open enquiry workload and incorrect-assignment reassignments by salesperson
  • Qualified opportunities from assigned enquiries, where qualification is recorded
  • Completed orders and cost per order where source and sales records support the calculation

Recorded as a baseline before work starts, so every later report has an honest comparison.

Industry baseline

Keep the industry's wider measures beside the service measures.

Use the existing baseline to understand the context. These figures are not all targets for this engagement, and a change must not be attributed to the service without evidence.

  • Enquiries by source: WhatsApp, Maps, calls and walk-ins
  • Reply time to price and stock messages
  • Walk-ins that started as an online enquiry
  • Exchanges done against exchange enquiries
  • Repeat buyers from the existing bill book
  • Accessories and protection plans sold per handset

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.

Lead capture and lifecycle management
Choose lead capture and lifecycle management when enquiries do not reach one record, or stages mean different things to different people. Choose lead routing and assignment when records exist and the dispute is who should pick each one up.
Lead response and follow-up
Choose lead response and follow-up when the gap is the replies themselves: wording, reminders and next actions. Choose lead routing and assignment when replies are fine for those who send them but some enquiries wait because nobody is sure whose they are.
Territory planning
Choose territory planning when you need to redraw which accounts and areas belong to which salesperson, based on potential. Choose lead routing and assignment when territories are settled and the need is day-to-day rules for each new enquiry, including absence cover.

A sample of the output

A routing rule sheet says who gets which enquiry, and what happens when that person is away.

This is a rule sheet for a pump dealer with several branches. Read each row as one condition: who receives the enquiry, who takes it if that person is unavailable, and any exception.

Illustrative example, not client data. Yours is built from your own records.
ConditionAssigned toFallbackException
Enquiry names a product lineProduct specialistSales managerManager reassigns when the specialist is on leave
Enquiry from a town with a branchBranch sales leadNearest branchExisting customers go to their account owner
Enquiry with no place or productSales managerShared deskManager classifies, then reassigns
Repeat contact from an existing customerAccount ownerAccount owner's coverNever enters the rotation
Project enquiry of unusual sizeSenior salespersonOwnerFlagged on the manager view

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.

Names, areas and product responsibilities
Rules assign enquiries to people, so every salesperson, branch and specialist needs a clear area or product. A simple list will do. Where responsibilities overlap, the rule sheet marks the overlap and waits for your decision.
A decision on fair distribution
Rotation settings depend on whether enquiries are shared equally, by skill or by capacity. Decide the principle. Without it, the setup falls back to plain rotation, which can frustrate the team members who handle harder work.
Admin access to the enquiry systems
Assignment is configured where enquiries land: CRM, sheet or inbox. Admin rights are needed to set it. Without admin access, we write a manual handoff process instead of automation, and your team applies it by hand.
How leave is announced and covered
Cover rules need to know how absence is announced and who covers whom. Tell us how leave is arranged today. Without that, fallback rules may point to people who are away, and enquiries wait unseen.
A ruling on returning customers
Say whether account ownership or location wins when a returning customer contacts a different branch, and who is told. Without that ruling, such enquiries bounce between people, the customer notices the confusion, and the record shows several owners.

Marketing and sales together

The salesperson receives the enquiry with ownership already decided.

The handoff record contains the buyer's available contact details, source, routing information, assigned owner, and arrival time. The salesperson is responsible for the next reply; the manager receives exceptions requiring a decision. Keeping source information on the record lets marketing enquiry counts be compared with qualified opportunities and completed orders, rather than treating an assignment as a sale.

Decisions to make before the work starts

  1. Source access and tool limits

    Available fields, CRM permissions, and plan features determine what can run automatically. We confirm these dependencies before committing to a route; new integrations or wider CRM implementation require separate scope.

  2. Approved ownership and usable records

    Your sales lead must resolve competing ownership claims and approve the coverage list. Missing locations or inconsistent product names weaken routing; extensive data cleansing is separate work.

  3. Coverage and ongoing responsibility

    Branches, source variations, and exception rules affect the work required. Your nominated manager owns availability updates after handover unless ongoing administration is agreed separately. For regulated enquiries, your own compliance reviewer must approve information access and handoffs.

How it works

How lead routing and assignment 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. 1

    Current handoff review

    We trace recent enquiries from arrival to assignment and first reply. Your sales lead confirms where ownership breaks down and which sources belong in the scope.

  2. 2

    Ownership decisions

    You approve the routing criteria and their priority. Existing account ownership, specialist involvement, and branch responsibility are resolved before configuration begins.

  3. 3

    Intake and access approval

    We identify missing fields and check the permissions needed to change forms or assignment settings. Your nominated owner approves changes, including any manual steps required by tool limitations.

  4. 4

    Test assignment sign-off

    Sample enquiries cover normal routes and exceptions, including unavailable owners. Your sales lead checks the results against the written rules and approves corrections before live use.

  5. 5

    Live handover

    We check the initial live assignments and hand the exception view to the responsible manager. Rule changes and reporting arrangements follow the written scope rather than an assumed ongoing support commitment.

Approval and acceptance

Use an observable check before accepting an output.

These are proposed review checks for the named outputs. Agree the final conditions in the written scope, then record any missing requirement before accepting the handover.

  • Routing rules document

    Walk the selected record through the proposed steps. Identify who acts at each handover, what information they receive, and how an exception is assigned without inventing a missing step.

  • Intake field specification

    Inspect a sample record against the original information. Check required fields, duplicate handling, the responsible owner, and who is permitted to access it.

  • Assignment configuration

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Fallback and reassignment rules

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Rotation and capacity settings

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Manager assignment view

    Trace the output back to the selected source record. The reviewer distinguishes confirmed information from assumptions and records any unmet requirement before accepting the handover.

  • Assignment handover notes

    Walk the selected record through the proposed steps. Identify who acts at each handover, what information they receive, and how an exception is assigned without inventing a missing step.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

How is lead routing and assignment scoped for mobile phone stores?
Industry membership alone does not establish fit. The service exclusions, your operating model, and the records available determine the scope after your requirements brief. Define the process and access permissions before changing software settings or adding automation.
Do we need to buy a new CRM?
Not necessarily. We check what your existing CRM plan supports before proposing automation. A shared sheet or a managed WhatsApp handoff can carry the same ownership rules, but someone must take responsibility for checking and updating it.
Can you assign enquiries from IndiaMART and WhatsApp automatically?
Only where your receiving tools provide the required access and assignment functions. We check each source separately rather than promising that every channel can be connected. Unsupported sources need an agreed manual handoff or separately scoped integration work.
Should every salesperson get the same number of enquiries?
No. Equal numbers can send technical enquiries to the wrong person or overload someone with fewer working hours. Your sales lead approves who is eligible first, then how enquiries rotate within that group.
What happens when an existing customer contacts another branch?
You decide whether the account owner or the receiving branch takes responsibility. We record that priority and the handoff needed when another specialist must contribute. The same rule applies when a repeat enquiry arrives through a different source.
Will routing also qualify leads and chase buyers?
No. Routing decides who owns the enquiry; qualification decides whether it is a real opportunity, and follow-up governs what happens after contact. Those services can be scoped separately if the assigned salesperson still lacks a clear response process.

Continue your review

Compare the service scope and the related work.

The scope, responsibilities, fee, reporting frequency, and term are agreed in writing after the requirements brief and conversation. Tell us what you need.

Your brief

Tell us what you need, and we will read it before we call.

Eight short steps about your business, what you want and who decides. Most questions are a tap, and you can skip any you would rather answer on the call.