It's mid-afternoon, in the lull between lunch and dinner service. A hunter parks outside a family-run trattoria she visited last week and rings the owner, who has finally sat down. They spend twelve minutes on commission, menu photos and a launch date. That night, after the kitchen closes, the owner calls her back on WhatsApp with one more question.
The next morning, the CRM record for that trattoria shows a single entry: the visit, eight days ago.
For food marketplace sales teams, this is normal. Calls with restaurant owners happen on reps' own mobiles and on WhatsApp, and a CRM has no way to see them unless something on the phone sends them across. Fixing that doesn't require a new dialer or a new number. On Android, an app like Salestrail can log SIM calls and WhatsApp voice calls to the restaurant's CRM record as they happen. iPhone coverage is narrower: outgoing calls placed through the Salestrail app are logged, and incoming calls, WhatsApp calls and recording are not covered.
Below, we follow a restaurant deal through its three phases (signing, launching and keeping the restaurant), look at where each phase loses its calls, and finish with three questions that tell you whether automatic call logging fits your team.
Selling to restaurants means working around service. Owners and managers won't take a sales call at the height of lunch or dinner, so hunters work the edges of the day: mid-morning prep, the afternoon lull and late evening once the doors close. Those are also the hours a hunter spends on the move between visits, nowhere near a laptop.
Figure: The restaurant clock: hunters reach owners in the quiet hours around lunch and dinner service, usually from their own mobile or WhatsApp. Illustrative; hours vary by restaurant and market.
Owners also tend to deal with a person rather than a company. They save the hunter's number after the first visit and use it whenever something comes up, often as a WhatsApp call. The conversations that move a deal forward arrive on the rep's own phone, at times nobody planned.
None of this passes through the CRM. It hears about a call only if the rep types it in later, and after a day on the road that means a line or two from memory, or nothing.
A restaurant rarely signs on the first call. There's the introduction, the visit, follow-ups on commission and delivery area, and often a final call where the owner says yes. The visit usually gets logged because it was planned. The calls around it, which carry the actual negotiation, mostly don't.
After the contract, someone has to collect the menu, photos, opening hours and payout details, and agree a go-live date. That work runs on quick calls and WhatsApp, frequently with whoever is free in the kitchen. If those calls aren't on record, nobody can see which restaurants are stuck before launch, or why.
Once the restaurant is live, it passes to an account manager, who calls about order volumes, promotions and, sooner or later, commission. Those renegotiations go better when the account manager knows what the hunter agreed. If the hunter's calls never reached the CRM, that context went with her.
Figure: A restaurant deal passes from hunter to onboarding to account manager. Logged calls travel with the restaurant; calls left on phones are lost at each handover. Illustrative.
Each missing call is a small gap in a restaurant's record. Over a month of visits, those gaps add up in five ways.
A pipeline you can't read. When a restaurant's record shows a visit and then nothing, a manager can't tell a dead lead from a deal that is one call from closing. Forecasts for new restaurants going live end up resting on what hunters remember.
Two pitches to one owner. Hunters on neighbouring routes, or a hunter and an account manager, can call the same restaurant without knowing it, sometimes offering different terms. It makes the platform look disorganised to the person you're trying to sign.
Launches that stall quietly. A restaurant waiting on one missing document can sit in limbo for weeks, because the calls chasing it are invisible to everyone except the rep making them.
Cold handovers. When a hunter changes territory or leaves, her restaurants go to someone who has to start the conversation again, often with an owner who has already explained everything once.
Coaching from anecdote. Without knowing how many calls each rep makes, how many connect and how long they last, a manager can't see who struggles to get owners on the phone and who gets them on the phone but can't close.
Figure: The unlogged calls bill: what a restaurant onboarding team pays when calls stay on reps' phones. Illustrative; no figures implied.
With Salestrail running on a hunter's Android phone, the calls she already makes are captured in the background and sent to your CRM. That covers SIM calls from the phone's own dialer and voice calls on WhatsApp and WhatsApp Business. Each call lands on the CRM record with the matching phone number, along with when it happened, how long it lasted, whether it connected and which rep was on it. She doesn't switch apps, and owners still see the number they saved. WhatsApp messages are not read or stored.
That changes what managers see in each phase. During signing, they can see call activity on every restaurant in negotiation, as well as the visits. During launch, the onboarding team's chasing calls show up against each restaurant waiting to go live. And when an account manager opens a restaurant's record months later, the hunter's calls are already there.
Salestrail connects to Salesforce, HubSpot, Zoho CRM, LeadSquared and Microsoft Dynamics, and to other systems through its Push/Pull API and webhooks. Its caller ID feature looks up incoming numbers in the CRM, so a rep can see which restaurant is ringing before picking up.
One practical point: matching runs on phone numbers, so store owners' numbers in a single format with the country code. Calls from numbers that aren't in the CRM yet are handled according to your integration settings, and they stay visible in the Salestrail dashboard.
|
Situation |
Android |
iPhone |
|
Hunter rings an owner from the normal dialer |
Logged automatically |
Not logged; dial from the Salestrail app instead |
|
Owner calls the hunter back |
Logged automatically |
Not logged automatically; add it by hand |
|
Owner calls on WhatsApp or WhatsApp Business |
Voice call logged automatically |
Not supported |
|
Recording a pitch for coaching |
Possible; depends on the handset and its settings |
Not supported |
Recording is optional. On Android, SIM call recording relies on the phone's built-in recorder, and WhatsApp calls are recorded through Salestrail's own Recorder app. Setup for each platform is covered on the Salestrail mobile app page.
It isn't the right answer for every team. Three questions usually settle it.
Where do your reps make their calls? If they sit at desks and dial through a cloud phone system that already writes to your CRM, most of their calls may be covered. Restaurant hunters on the road usually aren't in that position.
Do owners call back or ring on WhatsApp? If they do, a desk dialer misses those calls, because they go to the number the owner saved: the rep's own mobile.
Which phones does the team carry? On Android, SIM and WhatsApp voice calls are both covered. On iPhone, only outgoing calls placed through the Salestrail app are logged, so a team that is mostly on iPhone will still have gaps.
They don't have to. Salestrail lets you set office hours and choose which SIM is tracked on a dual-SIM phone. Individual calls can be untracked by the rep, and role-based access limits who sees call data. If your team calls owners late in the evening, set the hours to match.
No. On Android, reps keep calling from the number owners already have saved. There is no virtual number and no VoIP line.
On Android, voice calls on WhatsApp and WhatsApp Business are logged like any other call. Messages are not tracked, and WhatsApp calls are not tracked on iPhone.
Their outgoing calls are logged when they dial from the Salestrail app. Incoming calls have to be added by hand, and calls can't be recorded on iPhone.
Calls logged to the restaurant's CRM record stay on it, so whoever takes over can read the whole trail. Anything that was never logged stays on the old phone.
On Android, yes, depending on the device. Recording and consent rules differ from country to country, so check with your legal team and tell owners when a call is recorded. Treat this as a pointer, not legal advice.
Picture that mid-afternoon call again, this time with calls logging themselves. The trattoria's record would show the twelve-minute conversation and the WhatsApp callback that night. The onboarding team would know a launch date had been discussed, and the account manager who inherits the restaurant next quarter would see the whole history before picking up the phone.
Learn more about how Salestrail logs restaurant calls to your CRM
If you'd rather watch it run on your own CRM, book a demo.