✦Selected work · Pacific Media's own product

Operlyn

We built Operlyn as a multi-tenant SaaS product around missed-call follow-up and review-request workflows, including the billing, telecommunications and support work needed to operate it.

ReactPostgresTwilioTelnyxStripe

Jordan M.New lead · from missed call

Missed call 2:14 PM · text sent in 4 sec

Hi, it’s Summit Concrete. Sorry we missed your call! We’re on a job. What can we help with?

Need a quote for a new driveway, about 600 sq ft.

Great. Can we come by Tuesday at 9am to measure?

Tuesday works 👍

Booked · Tue 9:00 AM

Job done! Mind leaving a quick review? ★★★★★

Illustration with sample data

CASE TYPEOwned product

DELIVERABLEProduct platform

CLIENT DISCLOSUREInterface shown with representative sample data

Before the build

The operating problem.

Home-service contractors can miss inbound calls while they are on a job, leaving customer inquiries waiting.

We built Operlyn as a multi-tenant SaaS product around missed-call follow-up and review-request workflows, including the billing, telecommunications and support work needed to operate it.

What we built

Missed-call text-back and a two-way SMS inbox
Review-request workflows and a lead pipeline
Stripe billing plus Twilio and Telnyx number provisioning
Edge functions with rate limiting, opt-out handling and delivery-event records

How it works

A clear path through the process.

A customer places an inbound call

The contractor's existing phone setup determines when the call is treated as missed.

The workflow sends a text

After required setup and messaging checks, the system can send the configured transactional response.

The team continues the conversation

Replies appear in a shared inbox so an authorized person can handle the inquiry.

Events remain recorded

Consent, opt-out and delivery events provide an operational history for the message flow.

What can be verified

Evidence, result and limits.

A useful case study should tell you what was built and where the evidence stops.

Implementation evidence

Multi-tenant account and permission structure
Telephony and two-way messaging integrations
Subscription billing and number provisioning flows
Rate limiting, opt-out and delivery-event handling

Demonstrated result

Operlyn demonstrates an end-to-end product architecture for phone events, two-way messaging, number provisioning, billing and account separation. Customer conversion outcomes vary and are not represented by the sample animation.