Design concept. Onderly is a fictional product created by Samoya.

For service businesses that run on a calendar

Your enquiries stop waiting for someone to get to them.

Onderly sits between the messages your business receives and the calendar it runs on. Enquiries get answered, qualified and put on the schedule while your team is still on site.

Set up on your existing phone number and inbox. Nothing is migrated and nothing is replaced on day one.

01 / The problem

The enquiry arrives. Then it sits.

Someone fills in your form at nine at night, or calls while both vans are out. The message lands somewhere: a shared inbox, a phone that nobody picked up, a note on somebody's dash.

By the time a person gets to it, the enquiry is a day old and has already asked two other companies the same question. Nothing in that chain is broken. It is just that answering has to wait for a human who is currently up a ladder.

02 / How it works

One path, from message to booked job.

Every enquiry enters the same route regardless of where it came from. Nothing depends on who happens to be near a phone.

The Onderly route from enquiry to booked job Enquiries from a form, a phone call or a message all enter one route: received, answered, qualified, then booked onto the calendar. Enquiries with no reply move to a follow up loop that rejoins the route at qualified. FORM PHONE MESSAGE 01 02 03 04 Received Answered Qualified Booked ALWAYS ON Follow up NO REPLY On the calendar WHERE IT COMES FROM THE ROUTE THE OUTCOME

Diagram, not a screenshot. It shows the route an enquiry takes, not a product interface.

03 / What it replaces

Four jobs nobody was hired to do.

  • Replaces

    Watching the inbox

    Somebody refreshing a shared mailbox between other work, and the gap on evenings and weekends when nobody is.

  • Replaces

    Asking the same six questions

    Where the job is, what it is, roughly when, and whether it is even the kind of work you take. Asked once, in the first reply.

  • Replaces

    Chasing people who went quiet

    The follow up that everyone agrees should happen and nobody has time to actually send on the third day.

  • Replaces

    Typing it into the calendar

    Re keying an address and a time from a message thread into a schedule, which is where the wrong postcode gets in.

04 / Fit

This is not for everyone.

It is a poor fit if your work arrives entirely through repeat customers and referral, if every job is quoted on site before anything can be scheduled, or if you already have somebody whose actual job is answering the phone and they are good at it.

It is a good fit if enquiries come in faster than anyone can reply to them, if the calendar is the thing your business actually runs on, and if the people who could answer are the same people doing the work.

If you are not sure which one you are, that is a reasonable first question on a call.

05 / Contact

See it running on your own enquiries.

A walkthrough uses your real enquiry types rather than a demo account, so you can see what would have happened to last week's messages. It takes about twenty minutes.