Support team dispatch app: send jobs to your team and track them live
Assign jobs to your support team, see who is free, and track their progress on your phone.
Run the team · Customer support team · Nigeria
Assign jobs to your support team, see who is free, and track their progress on your phone.
Who it's for
You service inverters, solar systems or POS machines for other businesses around Lagos. Two people on the customer care line, a handful of engineers on the road, and a supervisor trying to hold it together. It is Monday morning. Complaints piled up over the weekend on WhatsApp, two of your engineers are heading to the same street in Surulere, and the customer in Ajah who called on Friday is still waiting for somebody to show up.
The problem today
Everything lives in a notebook and the team group chat. The customer calls the office, my staff writes it down, then she forwards the address into the group and whoever sees it first answers. By afternoon I am the one calling each engineer to ask where he is and whether he has reached. Job cards come back days later, some without the customer's signature, some with no record of what was replaced. An engineer collects money for a part and I only hear about it when he is already back. And some complaints just die there. The customer calls again, angry, and nobody can tell me who was supposed to go and when.
What the app does, screen by screen
- Log a complaint — Your customer care staff takes the call and records the customer, the contact person, the address and area, the machine involved and what is wrong with it.
- Dispatch board — Your supervisor sees every open complaint and every engineer, who is free and who is already out, and sends each job to one person.
- My jobs — Each engineer signs in and sees only his own jobs for the day, with the address, directions and a WhatsApp button to reach the contact person before he sets out.
- On site — The engineer works through the checklist for that job type, adds photos of what he found and what he fixed, and gets the contact person to confirm before the job can close.
- Approvals — When an engineer needs a part or extra spend, he sends the request from site and you or the supervisor approve or decline it from your phone.
- Day view — You open one screen and see the whole day: what is still unassigned, who is on what, what is done and what is running late.
Who uses it and what it keeps track of
- Customers — Business name, contact person and phone, address and area, the machines or installations you service for them, and their past complaints. Desk staff, supervisor and owner see all of it. An engineer only sees the customers on his own jobs.
- Jobs — What was reported and by whom, the area, the engineer it was sent to, the stage it has reached, when it was opened, started and closed, notes and photos. Visible to the supervisor and owner, and to the engineer holding it.
- Team — Name, phone, role, the areas the person covers, and whether they are free or on a job right now. Set by the owner, seen by the supervisor.
- Checklists and sign-off — The steps for each job type, what the engineer ticked, the photos he added, and the name of the person on ground who confirmed the work. Kept with the job and never editable after closing.
- Spend requests — What is needed, the amount asked for, who asked, who approved or declined, and the receipt afterwards. Only the supervisor and owner see this.
What it changes for the business
Two engineers stop landing on the same street while another area waits. Nothing sits unassigned, because an unassigned complaint stays on the dispatch board where everyone can see it. You stop calling round to ask where people are. When a customer rings, your desk staff can say who is coming and when, without putting them on hold. Every job carries a record of what was found, what was replaced and who confirmed it, so return trips and arguments over money reduce. And your supervisor's morning runs on one screen instead of the group chat.
The one decision that matters
The one to settle is who closes a job. If the engineer closes it himself, dispatch moves fast, but you will keep arguing with customers who say nobody came or the fault is still there, and you will pay transport twice for the return trip. If a job only closes when the person on ground confirms on the engineer's phone, with their name and a photo of the work, you have proof and your return trips reduce. Go with customer confirmation, and add one escape: when the contact person is not around, the engineer notes it and the supervisor closes the job himself. Without that escape your engineers will start cutting corners just to clear jobs off their list.
What to build first, and what can wait
Start with the part that stops jobs from getting lost: logging a complaint, assigning it to an engineer, his job list for the day, the on-site checklist with photos and confirmation, and your day view. Approvals can be a plain yes or no at first. Receipts, spend reports, live location on a map and a page where the customer checks their own complaint can all come later, once the team is using the app every day and you know what they really need.
How BooDoo builds it
You describe the team, the stages a job passes through and who should see what, in plain words, and BooDoo builds it. It builds the database and the sign-in, so your desk staff, your supervisor and each engineer open the same app and land on different screens. The same request gives you a website on its own live address and an Android app you can publish on Google Play under your own account for the engineers' phones. Maps for addresses and WhatsApp buttons that open a chat come from ready integrations. Later you describe the change and it changes. If you would rather not build it yourself, BooDoo Launch builds it for you.
How you'll know it works
A customer calls to ask about their complaint and your desk staff answers there and then, from the screen, without first calling the engineer to find out where he is.
Build it
Paste this in and it gets built.
I run a company in Lagos that services inverters, solar and POS machines for other businesses, and I need an internal app for my team. My customer care staff should log each complaint with the customer, the contact person, the address and area and what is wrong, then my supervisor assigns it to an engineer and can see at a glance who is free and who is already out. Each engineer signs in and sees only his own jobs for the day, with the address, directions and a WhatsApp button to reach the customer before he goes. On site he ticks a checklist, adds photos, and the person on ground confirms with their name before the job closes. If he needs money for a part he sends a request and I approve or decline from my phone. Give me a manager screen for the whole day, showing what is open, what is done and what is running late. A website, and an Android app for the engineers.
Paste that request and it gets built, with a real database, sign-in and a phone app. You can change anything afterwards.
Ready-made apps like this
Try one live, then copy it into your workspace and make it yours.
Helpdesk software →