Customer messaging connected to the service job
The moment a technician texts a customer from their own phone, that conversation leaves your business. You can’t see what was promised, you can’t settle an argument about it, and when that technician moves on the whole thread walks out of the door with them. Opsler keeps it on the job: two people, one piece of work, zero phone numbers exchanged, and a record that is still there next year.
Included on the free Budding plan (2 seats, 50 jobs a month) and on Pro at $25/seat/month
One thread per job between the customer and their technician — a reply lands in the thread and flags the job together.
Who can join a job conversation
Two people: the customer, and the technician assigned to that job. A technician customer chat with exactly those two participants is narrow on purpose, and the narrowness is the feature. There is no group thread to get noisy, no third party to add by accident, and nothing a customer can scroll back through except the conversation about their own job. Neither side ever sees the other’s number, so the relationship stays with your business rather than with whoever happened to be on the van that morning.
This is field service messaging in the literal sense — a channel that exists because a job exists, and that closes when the job does. If your office needs to speak to a customer about something bigger than the visit, that is a phone call or an email, and it belongs outside this thread anyway.
How customers access the conversation
They tap the link in their job notification and start typing. No password to create, no app to download, no account to abandon halfway through the signup form. Removing the login is most of the reason a customer sends a message instead of ringing you at four in the afternoon — every extra step between a question and an answer converts into a phone call somebody has to take.
The same link opens the rest of their customer portal — the current job with its status and ETA, past visits at that address, and invoices with a line-item breakdown. The message thread sits alongside all of it, which means most of what they were going to ring about is already on the screen in front of them.
How technicians and office staff reply
The assigned technician answers from inside the Opsler app, on the job they are already looking at — no app switching, no copying an address into a different window, no personal number handed out. Your office runs on a separate internal team messaging channel for dispatch, handovers and everything else staff need to say to each other during a working day.
Keeping those two channels apart is worth doing on purpose. The things a dispatcher says to a technician mid-job — the running commentary, the pricing talk, the customer’s history with you — are things you would never choose to publish. Two separate channels means you never have to remember which window you are typing into.
Message delivery and status behaviour
Read receipts run in both directions, which quietly removes two arguments a week. Your office stops wondering whether the message landed, and the customer can see the technician has read the gate code before they set off. Messages are text, up to 2,000 characters each — long enough for an access instruction, a parking note or the reason a part is coming on Thursday — timestamped and stored on the job the moment they are sent.
Because every message is stamped and attached to the work, “nobody told me” becomes a question you can answer in ten seconds instead of a conversation you lose on principle.
Photos, files and job context
Visual evidence lives on the job, which is exactly where you want it a year from now. The job’s own photo documentation makes a before shot and an after shot part of finishing the work, and the customer sees both in the same portal as the conversation. Nothing has to be re-sent, re-found or scrolled back to.
The message thread itself carries text rather than attachments. That is a deliberate split: a photo pinned to the job record still turns up when someone searches that address in eighteen months, and a photo buried three hundred messages up a chat thread does not.
Notifications that land on the job, not in a personal inbox
A new message pushes a notification that opens the job straight onto the thread, plus an unread count sitting on the job itself. A technician who picks the phone up between two calls sees which job is waiting on them, not a list of alerts to triage. Everything routes through the app and the portal link, so there is one place a customer message can arrive and one place it can be answered.
Retention, permissions and privacy
Completing a job locks its thread as a permanent record. Both sides keep the full history and neither can add to it, so what was said during the work is fixed at the point the work finished, and nothing is deleted. If a dispute ever turns up six months later, the version of events you have is the one that was written at the time by both parties.
A customer who wants something else afterwards books a new job rather than adding to a closed thread — which is the difference between a request that gets scheduled and one that sits unread at the bottom of a conversation nobody opens any more.
What you get, on every plan
Job-linked messaging is not an upgrade, an add-on or a communications tier. It is part of the job record on the free plan and on Pro alike.
| What you get | Opsler | Detail |
|---|---|---|
| One thread per job, owned by the business | Yes | The customer and the assigned technician, on the job record — not on anyone's handset |
| Nothing for the customer to install | Yes | They tap a no-login link in their job notification and the conversation is there |
| Read receipts in both directions | Yes | Every message records when it was read, so nobody guesses whether the gate code landed |
| The technician is told immediately | Yes | A notification opens the job straight onto the thread, with an unread count on the job itself |
| The history outlives the job | Yes | Completing the work locks the thread as a permanent, timestamped record. Nothing is deleted |
| Included on every plan | Yes | Free Budding included — 2 seats, 50 jobs a month. Pro is $25/seat/month with no minimum |
Pro is $25 per seat per month, no seat minimum, with a 14-day trial that doesn’t ask for a card. There is no per-message charge and no tier above the one you are on.
Where job messaging ends and a helpdesk begins
Most customer communication software is built around a support queue: a shared inbox spanning email, text and web chat, tickets with assignment rules, a bot fielding pre-sale questions. That is a different category solving a different problem, and if a queue is genuinely what you need, it is worth knowing now. What Opsler owns is narrow and specific: the conversation between one customer and one technician about one piece of work, attached to the record of that work for as long as it exists.
For a field service business, though, most customer contact is not a support ticket. It is one question about one visit — where are you, can you do the back door too, the side gate is padlocked. Answer those on the job, in front of the work, and the shared inbox stops being the thing you were missing.
Customer messaging software questions
In Opsler, it is a conversation that belongs to the job rather than to a person: the customer and the assigned technician message each other on the job record, the customer through a no-login portal link and the technician through the Opsler app. Nobody exchanges a phone number, and the conversation is still attached to that job in six months when someone needs to read back what was agreed.
No — deliberately. The job thread has exactly two participants: the customer and the person doing the work. Your office coordinates with technicians through Opsler's separate internal team messaging instead, which keeps dispatch chatter, running commentary and pricing talk out of a conversation the customer can read.
No. Text messaging is a planned bring-your-own-provider option and isn't part of Opsler today. Nothing is masked or proxied either, because no phone number is involved in this flow at all — messaging runs entirely through the portal link and the app. If a shared SMS inbox is the deciding feature for you, this is worth knowing before you sign up rather than after.
Not inside the message thread — it carries text, up to 2,000 characters per message. Photos live on the job record instead, where before-and-after shots are part of finishing the work and are visible to the customer in the same portal. That is the more useful place for them: a photo attached to the job is still findable a year later, and one buried in a chat thread is not.
Nothing extra on any plan. It is included on the free Budding plan alongside 2 seats and 50 jobs a month, and on Pro at $25 per seat per month with no seat minimum and a 14-day trial that does not ask for a card. There is no communications tier and no per-message charge.
Ready to Run Your Business Without the Chaos?
Scheduling, dispatch, estimates, invoicing, customer portal, and a free branded website — start completely free, upgrade to Pro when you scale.
Free forever on the Budding plan. No credit card required.