If you are worried that your field team will push back the day you introduce a tracking app, you are right to be. It happens often enough that it is worth planning for rather than hoping against. The good news is that resistance is predictable: in almost every case it comes down to four specific things, and all four can be handled in the first two weeks. Below is what actually causes refusal, a two-week rollout sequence that works for small teams, and a set of ready-to-use templates in English, Hindi and Bengali you can copy and send today.
The biggest single trigger, and worth separating from everything else. A rep who is fine with check-ins can still object strongly to company software on a phone they paid for. The objection is about ownership, not tracking — so explaining what the app does never lands, because that is not what they asked.
When an app appears with no explanation, people fill the gap themselves and rarely fill it charitably. What they conclude is “management thinks we are lying.” Once that lands you get quiet non-use rather than open refusal, which is much harder to fix.
A real complaint, not an excuse in disguise. A rep on a rural beat with a mid-range phone has a legitimate problem if an app polls location continuously all day. Treat it as a technical issue to solve, not resistance to overcome.
If the only visible consequence is being marked absent or having an expense questioned, adoption decays within a month. People keep using systems that pay them back. Faster expense settlement and proof of visit already exist in most field apps — they just need to be said out loud.
The most common mistake is going company-wide on day one. Rolling out to one territory first lets you fix problems while they are small, and gives you a group of reps who can tell the others it is fine.
| When | What you do |
|---|---|
| 3 days before | Send the announcement message. Do not install anything yet. Let people ask questions first. |
| Day 1 | Install with one territory or one team of 10–15 reps. Walk each person through it in person or on a call. Do not send a download link and hope. |
| Days 2–5 | Watch for practical problems — battery, GPS showing the wrong location, people who cannot find the check-in button. Fix these before going wider. |
| Day 7 | Settle the first set of expense claims through the app, visibly and quickly. This is the single most persuasive thing you can do. |
| Week 2 | Expand to the rest of the team. Ask two reps from the pilot group to answer questions from the new group. |
| Month 1 | Set an adoption target rather than a rule — around 70% daily check-in compliance in month one, 80% in month two, 90% by month three. |
A phased target instead of immediate full compliance gives you room to coach rather than discipline, and it means the first month is not spent in confrontation.
Everything below is meant to be copied, edited and sent. Replace the text in square brackets with your own details.
Send this three days before installation, on whichever channel your team actually reads — for most Indian field teams that is WhatsApp, not email. Keep it as one message rather than an attachment.
Team,
From [date] we will start using an app called [app name] for daily attendance, check-ins and expenses.
Why we are doing this: right now your visits, attendance and expense bills are spread across WhatsApp messages, phone calls and registers. That means expense claims take longer to settle than they should, and sometimes work you have genuinely done does not show up in the record at all.
What it will do for you: your attendance is recorded automatically so it cannot be disputed later, your expense claims go through with the bill attached and get settled faster, and if a client ever says you did not visit, you will have a record that you did.
What it will not do: it does not track you after you log out for the day, it does not run on holidays or weekly offs, and it does not read your personal messages, photos, calls or contacts. Location is recorded only during working hours after you log in. And when you leave the company, your account is removed and your records are deleted from the system.
[Name] will help each of you set it up on [date]. If you have any concern about this, speak to [name] directly before then. We would rather answer the question now than have you worried about it.
टीम,
[तारीख] से हम रोज़ की अटेंडेंस, विज़िट और खर्च के लिए [ऐप का नाम] नाम का एक ऐप इस्तेमाल करना शुरू करेंगे।
हम ऐसा क्यों कर रहे हैं: अभी आपकी विज़िट, अटेंडेंस और खर्च की जानकारी WhatsApp मैसेज, फ़ोन कॉल और रजिस्टर में बिखरी हुई है। इसकी वजह से expense claim सेटल होने में ज़्यादा समय लगता है, और कई बार आपका किया हुआ काम रिकॉर्ड में आता ही नहीं।
आपको इससे क्या फ़ायदा होगा: आपकी अटेंडेंस अपने आप दर्ज होगी, इसलिए बाद में उस पर सवाल नहीं उठेगा। खर्च का claim बिल के साथ जाएगा और जल्दी सेटल होगा। और अगर कभी कोई क्लाइंट कहे कि आप विज़िट पर नहीं आए, तो आपके पास सबूत रहेगा कि आप गए थे।
यह ऐप क्या नहीं करेगा: दिन का काम ख़त्म करके log out करने के बाद यह आपको ट्रैक नहीं करता। छुट्टी और weekly off के दिन यह नहीं चलता। यह आपके निजी मैसेज, फ़ोटो, कॉल या contacts नहीं पढ़ता। लोकेशन सिर्फ़ काम के घंटों में, log in करने के बाद ही दर्ज होती है। और जब आप कंपनी छोड़ेंगे, तो आपका अकाउंट हटा दिया जाएगा और आपका रिकॉर्ड भी सिस्टम से मिटा दिया जाएगा।
[नाम] [तारीख] को आप सबके फ़ोन में इसे सेट करने में मदद करेंगे। अगर इसे लेकर आपके मन में कोई सवाल या चिंता है, तो उससे पहले सीधे [नाम] से बात कर लीजिए। सवाल अभी पूछ लेना बेहतर है, बाद में परेशान होने से।
টিম,
[তারিখ] থেকে আমরা প্রতিদিনের অ্যাটেনডেন্স, ভিজিট এবং খরচের হিসেবের জন্য [অ্যাপের নাম] নামে একটি অ্যাপ ব্যবহার করা শুরু করব।
কেন করছি: এখন আপনাদের ভিজিট, অ্যাটেনডেন্স আর খরচের তথ্য WhatsApp মেসেজ, ফোন কল আর রেজিস্টারে ছড়িয়ে থাকে। এর ফলে খরচের টাকা পেতে দেরি হয়, আর অনেক সময় আপনার করা কাজ রেকর্ডেই ওঠে না।
আপনার কী লাভ: আপনার অ্যাটেনডেন্স নিজে থেকেই রেকর্ড হবে, তাই পরে তা নিয়ে প্রশ্ন উঠবে না। খরচের ক্লেম বিল সমেত যাবে এবং তাড়াতাড়ি সেটল হবে। আর কোনও ক্লায়েন্ট যদি কখনও বলেন আপনি ভিজিটে যাননি, আপনার কাছে প্রমাণ থাকবে যে আপনি গিয়েছিলেন।
যা এটি করবে না: দিনের কাজ শেষে log out করার পরে এটি আপনাকে ট্র্যাক করে না। ছুটি বা সাপ্তাহিক ছুটির দিনে এটি চলে না। আপনার ব্যক্তিগত মেসেজ, ছবি, কল বা কন্টাক্ট এটি পড়ে না। লোকেশন শুধু কাজের সময়ে, log in করার পরেই রেকর্ড হয়। আর আপনি কোম্পানি ছাড়লে আপনার অ্যাকাউন্ট সরিয়ে দেওয়া হবে এবং আপনার রেকর্ডও সিস্টেম থেকে মুছে ফেলা হবে।
[নাম] [তারিখ]-এ আপনাদের প্রত্যেকের ফোনে এটি সেট করে দিতে সাহায্য করবেন। এই নিয়ে কোনও প্রশ্ন বা দুশ্চিন্তা থাকলে তার আগেই [নাম]-এর সঙ্গে সরাসরি কথা বলে নিন। এখনই জিজ্ঞেস করে নেওয়া ভাল।
Note what the message spends most of its length on. Not features — what the app will not do.
Put this in writing before you install anything, and have each rep acknowledge it. A written policy is what turns a rollout from something that happened to people into something they agreed to. It also protects you.
[Company name] — Field Activity Recording Policy
Effective from: [date]
Who this applies to: [field sales team / named territories]
What we record: Check-in and check-out time and location, attendance, visit notes, expense claims and attached bills, and location during working hours after login.
When we record it: Only between login and logout on working days. Nothing is recorded on weekly offs, holidays or approved leave, or after logout.
What we do not record: Personal messages, calls, contacts, photos, browsing, or any activity outside the app.
Why we record it: To settle expense claims accurately and quickly, to maintain a reliable attendance record, to confirm client visits when required, and to plan territory coverage.
Who can see it: [names or roles — keep this list as short as it genuinely is]. It is not visible to other field staff.
How long we keep it: Location data is kept for a maximum of 12 months. Attendance, visit and expense records are kept for as long as you work here. When you leave and your account is removed, your records are deleted from the system.
Your access: You can view your own recorded activity at any time from within the app.
Questions or concerns: Contact [name, role, phone].
Acknowledged by: ______________________ Date: __________
In Twib, location data is cleared automatically after up to 12 months. Attendance, visit and expense records stay for as long as the account does — they are removed when you remove the employee. So the retention line in your policy is only true if removing a leaver is part of your exit checklist. It also stops you paying a licence fee for someone who no longer works for you, which is worth checking on its own.
This template is a practical starting point, not legal advice. If you are unsure how India's data protection rules apply to your situation, have your policy reviewed by a professional before you roll it out.
Give this to whoever is doing the installation. Most refusals happen because a manager was caught off guard by one of these questions and gave a defensive answer.
| Question | What to say |
|---|---|
| Are you watching me all day? | No. It records location between login and logout on working days only. After you log out, nothing is recorded. You can check this yourself in the app. |
| Can you see where I am on Sunday? | No. It does not run on your weekly off, on holidays, or on approved leave. |
| Will it drain my battery? | It records at intervals rather than continuously. If you find it draining your battery faster than normal, tell us — that is a settings issue we can fix, not something you should have to live with. |
| What if there is no network where I work? | It keeps working offline and syncs when you get network again. You do not lose your check-in. |
| Why on my personal phone? | Honest answer: because issuing company phones to the whole team is not affordable for us right now. That is why we have written down exactly what it records and what it does not, and why it stops at logout. If you are still not comfortable, come and talk to me. |
| What if the GPS shows the wrong place? | It happens, usually indoors or in poor network. Tell us and we correct the record. Nobody gets penalised for a GPS error. |
| Can it read my WhatsApp or photos? | No. It cannot see anything outside the app. |
| What happens to my data if I leave? | When the company removes your employee account, your records are deleted from the system. Location history is in any case kept for a maximum of 12 months. |
Claims submitted through the app get settled within [X] days. Claims sent by WhatsApp go into the normal queue. The first person who gets paid quickly will tell everyone else.
A small monthly incentive tied to visit or beat adherence, rather than a penalty for missing it. A modest bonus outperforms a penalty of the same size, every time.
Attendance recorded in the app is final and not open to dispute — which protects the rep at least as often as it protects you.
This is the step most rollouts skip, and it is the difference between an app people use for three weeks and one they use for three years. Frame all of it as something the rep earns, not something they avoid losing.
You will usually have one or two. Work through it in this order rather than jumping to the last step.
Announce before you install. Put the policy in writing. Start with one territory, not the whole company. Fix the battery and network complaints instead of arguing with them. Make sure the rep gets something out of it within the first month. Keep tracking inside working hours and be able to prove it.
Do those six things and refusal usually does not happen at all.
In practice most Indian SMBs do, because issuing handsets to a whole field team is not realistic. What matters is that you announce it in advance, put in writing exactly what is and is not recorded, keep tracking inside working hours, and give people a genuine route to raise a concern. Imposing it silently is what turns a manageable objection into a standoff.
No. For most teams it is worth budgeting for one or two handsets rather than a fleet — for a productive rep who genuinely will not have it on their own phone, for anyone on a handset too old to run the app properly, and for contract or temporary staff. That is usually one or two people, not twenty.
No. Location is recorded between login and logout on working days. Nothing is recorded after logout, on weekly offs or on holidays. Employees can see their own recorded activity inside the app, and live tracking is switched on by the user rather than silently by someone else.
Location data is kept for a maximum of 12 months. Attendance, visit and expense records are kept for as long as the account is active, and are deleted when the company removes that employee. Companies can also delete specific records at any time.
Around two weeks for a typical SMB field team. Announce three days before installation, start with one territory of 10 to 15 reps, spend the first week fixing practical problems, then expand. Set a phased adoption target rather than demanding full compliance on day one.
On a company-issued device, following a lawful and clearly disclosed work policy is an employment matter like any other. On a personally-owned phone the position is less clear-cut, and consent given as a condition of employment is weaker than most employers assume. In practice the faster route is to resolve the underlying objection — device ownership, unclear purpose, battery drain, or no benefit to the rep — rather than to escalate. This is general information, not legal advice.
In writing, three days before installation, on the channel they actually read — for most Indian field teams that is WhatsApp. Say what is recorded, why, what is not recorded, and what they get out of it. Announcing after installation, or not announcing at all, is what turns a manageable objection into a standoff. There is a ready-to-send message in English, Hindi and Bengali further up this page.
Adoption usually decays in month two, not month one, and the cause is almost always that nothing good has happened to the rep because of it. Call five people who stopped and ask what got in the way, fix the technical complaints publicly so the team sees that raising a problem produces a result, then connect the app to something they gain — usually faster expense settlement.
If you would like to talk through how this would work for your team and territory before you commit to anything, book a short call. We will walk you through the rollout, not just the software.