Skip to content

Two-way SMS

A real SMS inbox. Not a one-way blast.

Most shop software treats SMS as a one-way appointment reminder. A robotic blast goes out, and when the customer texts back, it ends up in a Twilio inbox no one checks. Pitlane's inbox is a real conversation surface. Left pane: every thread, sorted by recency, with unread badges. Right pane: the conversation with the customer plus a composer at the bottom. Type, hit send. The reply goes out from your dedicated shop number, not a generic short code.

1 thread

Per customer, every message

15s poll

New texts surface while you watch

Your number

Local 10-digit, not a short code

One inbox for every customer conversation.

When a customer texts your shop number, it lands in Pitlane's inbox as a thread tied to their contact record. When the next customer texts in, they get their own thread. No mixing, no guessing which "yes" was for the brake-job estimate.

The thread list shows you who's waiting on a reply at a glance. Unread badges. Most-recent first. Click a row to read the conversation and answer it. On desktop the conversation opens next to the list so you can scan the queue while you reply.

Reply where you are, with the customer's history in view.

The thread pane sits to the right of the list, full-height, with a composer at the bottom. Type a reply, hit Cmd-Enter or click Send. The composer shows your character count and the SMS segment count as you type, so a 200-character explanation doesn't quietly cost you two segments without you noticing.

Replies go through your shop's per-shop Twilio subaccount, so the customer sees your local 10-digit number. Not a shared short code that says "is this spam." Per-shop A2P 10DLC registration is automatic the first time you turn on SMS in Settings.

  • Two-pane on desktop (≥1024px), thread permalink on mobile
  • Cmd/Ctrl+Enter sends, multi-line composer auto-grows to 6 lines
  • Auto-polls every 15 seconds while a thread is open + on tab focus
  • Outbound messages show the segment count so long replies don't surprise you

New texts arrive without a page refresh.

While you're looking at a thread, Pitlane re-fetches the conversation every 15 seconds. When the tab is hidden, polling pauses to keep the connection footprint small. When you come back, a single focus event triggers a refresh so you're never looking at stale state.

The thread list refreshes on focus too. A customer can reply while you're in another browser tab, and when you come back to the inbox the unread badge will already be updated.

Mobile gets the same thread, on its own page.

The two-pane layout collapses on phones into a list-only view at /inbox. Tap a thread, you land on /inbox/[customer]. A dedicated thread page with the full composer + a back link to the list. The same polling cadence runs, so an advisor walking the floor can reply between bays without missing a beat.

How it works.

01

Enable SMS in Settings

Settings → SMS → register your shop on per-shop A2P 10DLC. Pitlane provisions a dedicated local 10-digit number under your shop's own Twilio subaccount. Approval typically lands within 1-3 weeks.

02

Customers text in

Every text your shop number receives lands in the inbox as a thread tied to the customer record (when the phone matches a contact). Unknown numbers still land. You can attach them to a contact later.

03

Reply where you are

Open the inbox, click a thread, type a reply, send. The customer gets a text from your shop's local number. The thread refreshes every 15 seconds so you see their next message without leaving the page.

This runs for your shop on a 30-day free trial.

Every feature on this page is included in the trial. No credit card. Live in under 10 minutes.

Questions about two-way sms.

What's the phone number my customers see?

Your shop's own dedicated 10-digit local number, registered to your business through per-shop A2P 10DLC. Not a shared short code, not a Pitlane-branded number. Customers can save you in their contacts and text you back at the same number.

Does it work on a phone?

Yes. Mobile collapses the two-pane into a list, and tapping a thread opens a dedicated thread page with the same composer and polling. An advisor on the floor can reply between bays.

How do replies stay in order if multiple people on staff are answering?

Every reply is logged with the user who sent it. The thread refreshes every 15 seconds while open, so two advisors working the same inbox see each other's outbound messages without stepping on each other. We do not currently lock a thread to one advisor. Staff coordination stays human, the way it works in the shop.

What if a customer texts in before they're in our contacts?

The thread still lands. The list shows the raw phone number until you attach the conversation to a contact (or create a new contact from the thread). No lost messages from walk-ins or strangers.

More features.