Callbacks stay visible
Write down who needs a call back, when it is due, and what happened. Nothing disappears into a notebook or text thread.
Built for the owner on the phone
Follow up without losing control.
GridHand gives a local service-business owner one calm place to track callbacks and review customer-message drafts before anything sends.
Controlled pilot · no autonomous outreach · no billing
Tuesday, July 22
Owner Operations
Needs your attention
Call James back
Brake estimate · due at 10:30 AM
Draft message
“Hi Keisha—thanks for trusting Speedy Brake today. Would you be willing to share how the visit went?”
RejectApprove once
The first useful version
Three jobs. One clear loop.
GridHand is intentionally focused. It helps the owner remember, review, and decide.
Messages begin as drafts
Missed-call and review-request follow-ups wait in one queue. GridHand does not contact a customer on its own.
The owner decides
Read, approve, or reject every customer-facing message. One approval applies to one message—never a blanket permission.
Approval first
Nothing reaches a customer until the owner says yes.
That rule is enforced in the interface and on the server. If approval cannot be verified, the message does not send.