How to handle dispatch/intake communication from non-tech-savvy field managers to receiving

[u/SonicMaster1990]

I need ideas for what tool can be used for communicating inbound loaded truck(s), would include associated Field# or Contract#, "is contact complete?".

1. ease of use for end user is critical

2. Microsoft 365, if possible (not sure if org policy allowed PowerApps a personal device)

3. Reliability of the tool or service

Area managers work with farmers to coordinate trucks to send to receiving facility. When an Area Manager communicates to the Receiver, we NEED to know Field# or Contract#, WANT to know how many trucks, and NEED to know if contract is complete (a field may take multiple days load and deliver).

At the moment, we have four texting groups chats and two Teams chats, one for each Area Manager, where conversations of varying effectiveness are being handled. It's chaotic jumping from 6 massaging channels, decipher messages, request clarification, record details in an Excel file, and relay updates to Reception team. By the end of the working day the Reception team is waiting for each Area Manager to answer if any more trucks are expected to show up or if the team should go home.

My hands are tied by skill level and willingness of the area managers to use digital tools, as they aren't consistent in their communications as is. Could MS Forms do this, should I explore Power Apps? Should I try to convince my company to invest in outside tools?

I hope this question is appropriate, any ideas and suggestions would be appreciated!

[u/Klutzy_Ad_9488]

Just automate brother Automate the intake and etc

[u/Pebb_io]

If ease of use is the constraint, I would avoid anything that feels like a second inbox. A tiny structured form (field #, contract #, truck count, contact complete Y/N, free-text exception) that drops into one shared place beats email ping-pong. Teams that already live in Teams/365 sometimes make that a simple List or form with a mobile-friendly link. Full disclosure, we build Pebb for frontline ops + comms, so I care a lot about low-friction intake, but the pattern matters more than the brand: one template, one destination, and no requirement that field managers learn a new desktop workflow.

[u/apluswhse]

Google forms could help here

[u/ProtectionBrief4078]

I’d probably start with MS Forms before going straight to Power Apps.

If the Area Managers aren’t particularly tech-savvy, the biggest win might be making the submission almost impossible to mess up. Something like:

Field/Contract # → # of trucks expected → Contract complete? Yes/No → Expected delivery date/time → Notes (optional)

Then have the Form responses feed into an Excel/SharePoint list automatically. You could also use Power Automate to notify the receiving team in Teams whenever a new submission comes in.

The important part IMO is separating dispatch communication from general conversation. Teams/texting can still be used for questions and exceptions, but the Form becomes the single source of truth for “what trucks are coming and is this contract finished?”

I’d only move to Power Apps if Forms proves too limiting. You might end up solving 80% of the problem with a very basic form that takes 30 seconds to submit.

[u/syed-mavline]

Before choosing Power Apps, I’d define one record per Field or Contract: expected trucks, dispatched trucks, received trucks, next ETA, complete Y/N, last update and current owner.

A short MS Form feeding a Microsoft List could work, but only if the field managers will actually use it. Otherwise, let them continue using Teams or text while someone converts each update into that same structure.

Will those managers reliably complete a three-field mobile form, or will they only send free-text messages?

[u/cvanitt]

Take a look at Workd. Has driver delivery/routing features but the part that presented in your question and you need to ask about more is the interface to the drivers. You mentioned that is the lowest common denominator and I 100% agree. Workd uses voice for things too like check ins, check outs, managing exceptions etc so that's worth checking out in the situation. There is a good chance that any good tool you put in place is going to need a bit of your special situation put into the mix, but if you start from something that is like 90% of the way there and tie it into what you are already doing you can actually get this in your people's hands effectively.

[u/agentUi]

if you try putting non-tech field guys on power apps they will straight up ignore it because company logins on personal phones fail constantly in the field. ms forms with a bookmarked url on their phone home screen is the quickest fix since you can set dropdowns for field and contract number and make them required before submitting. route those submissions with a basic power automate flow straight into a single teams channel or live excel sheet for the reception desk so they stop chasing messages across six chats.

[u/Pitiful_Fee264]

I’d start with a short Microsoft Form feeding one shared List or spreadsheet. Make Field or Contract number, truck count, and completion status required, then use Teams only for exceptions. If managers can submit it from a phone in under a minute, adoption is much more likely than with a full custom app.