Field sales CRM for reps who call first, then visit

• Visits are reported, not recorded

  A rep says they met six customers today. Without a check-in at each address, the manager has a message in a group chat and nothing to compare it with.

• The calls around a visit are lost

  The call that booked the meeting and the call that chased the order happen on the rep’s own phone, so the account’s history lives in one person’s call log.

• The next step depends on memory

  A customer who asked for a revised price on Tuesday hears nothing until they ring back, because the follow-up was written in a notebook.

• Accounts leave with the rep

  When a rep resigns, their customer list, notes and contact numbers go with their phone.

1. 11 / 5

   Accounts are assigned before the day starts

   Import each rep’s accounts from Excel or CSV and assign the list to them, while new enquiries from your website and ad forms are shared round-robin. The rep opens Tasks in the app to see who is due today.

2. 22 / 5

   The day starts with a check-in

   If your attendance policy asks for it, the day’s check-in reads the phone’s location once. Leave the distance limit from the office off for reps who start from home or the market.

3. 33 / 5

   A call confirms the visit

   One tap dials from the work SIM and the call is logged on the account. The outcome the rep picks can book the next follow-up and move the stage.

4. 44 / 5

   Check-in and check-out at the customer

   At the shop or office the rep checks in from the account. LumaKol reads the location once, shows “At the location” within 200 metres of the saved location or the distance away, and the check-out note records what was agreed.

5. 55 / 5

   The manager reviews the day

   Field visits lists each rep’s stops in order with time spent, the distance from each customer and a link to the route in Google Maps, and managers can open the same day for any rep in the app under More → Work → Visits. Check-ins whose location looks faked carry a red marker with the reason.

On Android, every call on the work SIM is logged on the right lead with its exact duration, including calls dialled from the phone’s own dialer. On iPhone, calls started from LumaKol are logged with an approximate duration measured by the app. Either way, the outcome is one tap away after each call.

• Field visits and day routes

  Check-in and check-out at the account with a purpose, a note and an optional photo, the distance from the customer’s saved location and a route per rep per day. Location is read only at those moments, never in the background.

• Attendance and breaks

  A day check-in with an optional location, typed breaks, shifts with late marks and leave requests, in the same app the rep calls from.

• Calls logged on their own

  Calls with customers on the work SIM attach to the account, so the history stays with the business when a rep moves on.

• Follow-ups and retry rules

  Each outcome can book the next call or visit as a dated follow-up, and retry rules bring back customers who did not pick up.

• Automation rules

  Share new enquiries round-robin, move the stage on an outcome and alert the manager when a follow-up on an account in Visit booked goes overdue.

• Reports, funnels and coaching

  Calls, connected calls and won accounts per rep, the stage funnel, and Reports → Attendance with check-in, check-out and breaks per person per day.

• CSV / Excel import

  Each rep’s account list from your billing software or old Excel sheets.

• Google Ads lead forms

  Lead-form extensions post straight into your workspace.

• Website webhook

  Any website or form tool can send leads to your workspace URL.

• Hosted forms

  A LumaKol form you can link from ads, bios and QR codes.

• IndiaMART

  Buyer enquiries from your IndiaMART account arrive as leads.

• Public API

  Create and update leads from your own systems.

Questions from field sales managers