Does lockbox MMS include carrier credit?

No. Priced by devices and SMS send volume. You use your own phone and operator SMS credit. The truck SIM still needs operator balance.

Can key-tag photos share the technician login OTP phone?

No. Isolate OTP from lockbox MMS so a morning open burst cannot starve door codes.

What fails before the radio?

Crop to the key tag, readable box id, MIME allow-list, job id. If APN will bounce it, keep the photo in the ticket and SMS the typed lockbox id.

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

Key Takeaways

Lockbox MMS is a cropped key tag — box id readable, one job id — not a porch panorama.
Type the lockbox id in the ticket; the photo is evidence if the key is disputed.
Door-code OTP never shares the lockbox-photo SIM.
Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Free is 300 SMS lifetime; Developer is 25,000 SMS per year.
This is our Android SIM gateway, not a CodeCanyon field-app. MCP is only a REST wrapper if you add it.
Developer Center owns live attachment fields.

Summary

A lockbox photo is a key tag, not a porch tour. Crop the label, type the box id in the ticket, and keep door-code OTP off this radio. Priced by devices and SMS send volume. You use your own phone and operator SMS credit.

If you cannot read the box id in the thumbnail, do not tax the carrier. Type the lockbox and keep the full frame in the job.

Lockbox crop vs OTP

Payload	On the truck SIM?	Fail closed
Cropped key tag	Yes, one frame + typed box id	Unreadable id or missing job id
Porch panorama	No — keep in the ticket	Always
Door-code OTP	Never	Always isolate

Key takeaways

Crop the key tag; type the lockbox id in the ticket.
If APN will bounce the crop, SMS the typed box id only.
Customer OTP never shares the lockbox-photo SIM.
Priced by devices and SMS send volume. You use your own phone and operator SMS credit.
Not a CodeCanyon field-app. MCP wraps REST if you add it.
Canary one cropped tag on a staff number before morning opens.

Context

Property techs use this field-service scenario to send one cropped key tag from a truck SIM after the ticket already holds the typed lockbox id.

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 tag-evidence, porch-archive, and door-OTP moments to separate radios before anyone attaches a raw gallery.

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 morning open as devices plus volume plus MMS-rate airtime. Free is 300 lifetime SMS; Developer is 25,000 SMS per year.

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 lockbox MMS only when crop rules, typed box ids, and door-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 Server guide, compare device and SMS volume pricing, open device setup guide, and confirm APIs in SMS API documentation.

Deep dive: production hardening

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.

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.