Does field-service MMS include carrier credit?

No. Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Picture messages still debit the truck SIM.

Can job photos share the technician login OTP phone?

No. Isolate OTP from dispatch MMS so a burst of completion photos cannot starve door-code or app-login sends.

What should fail before the radio?

Pixel budget, MIME allow-list, and a job id. If the APN will reject it, keep the file in the work-order system and send an SMS link instead.

Android SMS Gateway Scenario 57: Field service MMS attachments in practice

Key Takeaways

Field-service MMS is a job-close artifact: resized photos, not a second inbox for login codes.
Carrier APN and size caps fail closed — a 12MB before/after set will never leave the truck.
Customer job photos and tech-to-dispatcher MMS stay off the technician OTP SIM.
Priced by devices and SMS send volume. You use your own phone and operator SMS credit. MMS still meters platform volume and operator airtime, often at a higher carrier rate.
Free is 300 SMS lifetime on one device — prove a single resized photo, not a whole day’s jobs.
Developer Center owns live attachment fields; this playbook is APN and lane hygiene.

Summary

A tech closing a boiler job does not need a 12MB album on the customer’s phone. Field-service MMS is a resized proof photo or a one-page invoice — and it never shares a radio with the door-code OTP.Priced by devices and SMS send volume. You use your own phone and operator SMS credit.

If the APN will bounce the file, send an SMS link. The truck SIM is not a CDN.

Photo vs invoice vs OTP

Payload	On the truck SIM?	Fail closed
Job-close photo	Yes, resized, one image	Over APN size or missing job id
Invoice PDF	Only if the carrier accepts it	Else SMS + portal link
Tech / customer OTP	Never this chassis	Always isolate

Key takeaways

Resize job photos before the radio ever sees them.
APN and MIME caps fail closed; use a link if the file will bounce.
Technician OTP never shares the MMS dispatch SIM.
Priced by devices and SMS send volume. You use your own phone and operator SMS credit.
Developer Center owns live attachment fields.
Canary one resized photo on a staff number before a full route day.

Context

Dispatchers use this field-service scenario to send one resized completion photo from a truck SIM after the work order already holds the full album.

Radio reality still wins: offline phones and OEM killers break scenarios overnight.

Cross-link hub cornerstones instead of rewriting the product overview.

Keep examples conceptual until Developer Center confirms live request shapes.

Budget airtime for retries — failed loops still cost operator credit.

Core scenario guidance

Map job-complete, parts-delay, and customer-OTP moments to separate device pools before anyone attaches a raw camera roll.

Separate configuration mistakes from radio failures during incidents.

Write acceptance criteria before seasonal or clinic-hour traffic.

Prefer gradual rollout with feature flags when automation is involved.

Cost and ownership

Model a route day as devices plus send volume plus MMS-rate airtime on the truck SIMs. Free is 300 lifetime SMS — prove one photo, not forty jobs.

Failed retries still burn credit during scenario experiments.

Assign who owns SIM top-ups and spare handsets.

Keep marketing spend out of OTP device pools.

Operations

Daily checks: pairing health, battery, queue depth, and DLR anomalies.

After OEM updates or SIM swaps, re-test the scenario path end to end.

Keep a spare charged device ready for failover drills.

Name an on-call owner before unattended sends go live.

Security and compliance

Protect API keys per environment; rotate after contractor access ends.

STOP and consent still apply on promotional scenario lanes.

Avoid logging full OTP bodies into shared chat.

Verify webhook signatures and TLS on every callback path.

Decision guide

Ship field-service MMS only when resize rules, APN tests, and OTP isolation are written.

Delay if you cannot explain offline-phone behavior during peak hours.

If zero phone ops is mandatory, evaluate CPaaS for that lane.

If local SIM economics matter, harden the Android path and monitor airtime.

Checklist

Scenario moments listed with owners.
OTP vs marketing isolation confirmed.
Spare device funded and paired.
Canary on staff numbers passed.
Developer Center checked if API-shaped.
Webhook/DLR monitoring ready.
Airtime budget includes retries.
On-call owner named.
Rollback path documented.
Hub cornerstone reviewed.

Next steps

Return to how an Android SMS gateway works, compare device and SMS volume pricing, open device setup guide, and confirm APIs in SMS API documentation.

Deep dive: production hardening

Canary on staff numbers before customer OTP.

Battery exemptions and OEM killers dominate overnight reliability.

Cross-link Setup, Pricing, Downloads, and Developer Center with keyword-rich anchors.

If zero phone ops is mandatory, evaluate CPaaS for that lane instead.

Webhook signature verification is non-negotiable for scenario automation.

Document who owns SIM top-ups for multi-site scenario rollouts.

Prefer honest latency expectations over marketing claims about global SLAs on SIM paths.

Scenario playbooks still bill by devices and SMS send volume. You bring the Android phone and operator SMS credit.

Developer Center owns live API parameters. Scenario blogs teach process and failure modes, not endpoint catalogs.

Ecommerce webhooks must verify signatures before they trigger SMS sends.

Clinic reminders need consent records and STOP handling even when messages feel transactional.

Logistics ETAs should degrade gracefully when devices go offline mid-route.

Edtech OTP spikes at exam windows — capacity plan devices before the semester starts.

Fintech OTP is high-stakes: isolate devices, rotate keys, and avoid logging full codes.

Real-estate nurture is promotional; keep it off OTP SIMs and honor quiet hours.

Restaurant reservation SMS still needs STOP on marketing lanes.

SaaS onboarding OTPs should canary on staff numbers before paid scale.

Field-service dispatch needs two-way inbox ownership so techs are not double-booked.

Marketplace seller alerts need multi-device failover when a single phone is the SPOF.

NGO outreach must separate fundraising blasts from operational alerts.

Appointment businesses live on reminder deliverability the morning of the visit.

Bulk CSV import needs validation before radio send; bad rows burn airtime.

Scheduled SMS must survive device sleep and timezone mistakes.

Auto-reply and STOP protect promotional lanes — never auto-reply into OTP threads.

Dual SIM routing fails when slot maps drift after reboot without re-pair.

Multi-device failover only helps if spare phones stay charged and paired.

MMS attachments inherit carrier size and APN limits.

USSD requests are carrier- and region-sensitive; treat timeouts as expected.

Contact lists need consent metadata stored with the number.

OTP priority queues fail when marketing blasts share the same device pool.

Spare charged devices matter more than brochure SLAs when phones send the SMS.

Airtime surprise bills happen when bulk loops ignore radio pace.

OTP and marketing must stay on separate lanes on every scenario.

Never claim unlimited free cloud SMS credits with no device or volume meter.

Name an on-call owner before unattended schedules go live.