Apps · 2026-10-12

Jason on Sqyre Hub: the night desk that lives in your pocket

Jason on Sqyre Hub: the night desk that lives in your pocket

Jason is not a chatbot tab. On Sqyre Hub he is the floating orb. He answers, books, and follows up while you are on a roof.

The simple idea

After hours work used to mean the owner’s personal cell. That is how weekends die. Jason is the desk that can answer without giving away the evening.

On Sqyre Hub he is a floating orb, the same as the web app. He is not a fifth tab named Assistant that nobody opens. You tap the orb. You ask what is waiting. He already took the 9pm no cool.

If you had to explain it to a neighbor, you would say this. The shop phone still rings the shop. A person named Jason answers with your rates. You read the tickets in the morning on Hub.

A normal weekday

A plumbing shop closes at 5. At 9:14pm a homeowner calls about a supply line. Jason collects the address, a photo of the cabinet, whether they want the after hours rate or the morning window, and whether anyone is home. He does not guess $89 because that number felt friendly.

The owner is at a kid’s game. Hub notifies. The ticket is already a request with the photo attached. In the morning the tech opens Sqyre Team and the stop is on Routes.

That is the whole product. The night becomes a ticket. The ticket becomes a stop. Nobody transcribes voicemail at 6am.

What Jason is allowed to say

Jason can only say what you wrote down. A shop playbook is the desk when you are on a roof. Visit fee. After hours multiplier. Service area. The next open morning. The sentence for a house outside the cluster.

If the playbook is empty, Jason will sound like a generic phone tree. That is not an AI problem. That is an unwritten shop.

Train him on your rates. Quotes come from the price book. You set the prices. He builds and sends them, or he waits for your yes on Hub.

Voice, SMS, and email as one thread

A customer who calls, then texts, then emails is still one person. Timeline on Hub is that thread. Jason adds to it. You add to it. The tech’s job notes add to it.

See voice, text, and email as one thread. If those channels live in three inboxes, you will quote two prices.

The orb is a habit

Native Hub keeps Jason as an orb on purpose. Tabs are Home, Browse, Schedule, Timeline. Jason is always one thumb away, the way a good dispatcher is always in the shop even when they are not at a desk.

Do not hide him. Do not make a manager hunt Settings. If the night desk is annoying to open, you will go back to giving out your personal number.

What people get wrong

They let Jason say yes to same day work the truck cannot reach. That is how a good AI becomes a liar. The skip rule belongs in the playbook. Hub should show the shape of the day. Jason should offer Thursday on that street, not a fairy tale.

They also treat Jason as a toy for the website only. If he is not on the owner iPhone, he is not the night desk. He is a demo.

If you are training someone this week

Write three sentences: the visit fee, the after hours rate, and what to say when the house is outside the cluster. Put them where Jason can repeat them.

The only sentence the night is allowed to send is this one. We can come in the morning window, or we can come tonight at the posted after hours rate. Pick one.

Where this sits with the two apps

Jason thinks in Hub. Crews execute in Team. A scan, a photo, a clock punch: Team. A quote, a booking, a follow up: Hub and Jason.

Read two iPhone apps, one shop when someone asks why they cannot have a single login that does both jobs badly.

How Jason uses Hub without becoming a toy

The orb is always on the Hub chrome. You can be in Schedule and still tap Jason. You can be on a client and still ask what is unpaid. That is why it is not a tab. Tabs get abandoned. Dispatchers do not.

Voice, SMS, and email are channels, not products. Jason picks the channel the customer used. He books the window you already opened. He sends the quote from the price book. He follows up. He does not invent a same day arrival for a pin the crew will not reach.

Hub is where you read the night. Team is where the night becomes a stop. If you only train Jason and never open Team for the tech, you built a beautiful answering service that still leaves the truck lost.

A week of training Jason

Monday write the visit fee. Tuesday write the after hours rate. Wednesday write the skip rule for a far house. Thursday listen to one real call recording or transcript. Friday change the one sentence that caused a surprise.

Jason gets smarter when the shop is specific. Vague shops get vague nights.

The limit is the feature

A night desk that cannot say no will fill a Thursday you cannot staff. Put the no in the playbook. Hub’s schedule is the proof. Jason should read the proof. That is how a small shop stays a shop instead of becoming a rumor of availability.

What Jason should collect on a night call

Name. Callback number if different. Address including gate, floor, unit. What is wrong in their words. Photo if they can send one. After hours versus morning. Whether anyone is home. Whether water is off. Whether the system is under a plan.

If your playbook does not ask those, Jason cannot. Write them. HVAC needs refrigerant type if they know it. Plumbing needs whether it is a drip or a spray. Electrical needs whether breakers are tripped. Lawn can wait until morning almost always.

Tone

Jason should sound like your shop, not like a hotel concierge. Short sentences. The fee. The window. The no. Humor is optional. Clarity is not.

If he is too friendly, he will say yes. Friendly yeses are expensive.

Approvals

Some owners want every quote tapped in Hub before it goes. Some want Jason to send under a dollar cap. Both are valid. The orb is how you approve from a roof. Do not pick “I will look later” as a policy. Later is how a hot lead cools.

Transcripts

Read them. Not all. One a day for a week. You will hear the sentence that needs rewriting. That is training. AI without transcripts is a rumor.

Handoff to Team

A ticket Jason created must appear on Routes. If it does not, the night desk is a diary. The morning desk must be a stop. Test this once on purpose: fake a night request, see it on Team before 7am.

What Jason is bad at

He is bad at jobs you have not priced. He is bad at houses you have not mapped. He is bad at “just squeeze them in.” Those are human failures you should not outsource.

He is good at being awake. Use that.

The orb on a roof, in practice

You are on a ladder. A request lands. You cannot type a novel. You tap the orb. You ask what is waiting. Jason already took the 9pm no cool or he did not. If he did not, the playbook is empty or the night desk is still voicemail.

Voice, SMS, and email are channels, not products. Jason picks the channel the customer used. He books the window you already opened. He sends the quote from the price book. He follows up. He does not invent a same-day arrival for a pin the crew will not reach.

Hub is where you read the night. Team is where the night becomes a stop. Train both. An answering service that never becomes a Route is a diary.

What to write before you leave him alone

Visit fee. After hours multiplier. Service area. Next open morning. The sentence for a house outside the cluster. HVAC: refrigerant type if they know it, heat or cool, whether it is under a plan. Plumbing: drip or spray, water off, anyone home. Electrical: breakers tripped, burning smell, darkness. Lawn: almost always morning. Roofing: tarp versus tear-off, is anyone home, is it actively leaking into a room.

If those sentences are not written, Jason will sound like a hotel concierge. Friendly yeses are expensive.

Approvals from a pocket

Some owners want every quote tapped in Hub before it goes. Some want Jason to send under a dollar cap. Both are valid. The orb is how you approve from a roof. “I will look later” is how a hot lead cools.

Transcripts: one a day for a week. You will hear the sentence that needs rewriting. AI without transcripts is a rumor.

Handoff tests you should run on purpose

Fake a night request. See it on Team Routes before 7am. If it does not appear, the night desk is a diary. Fix the handoff before you advertise after hours.

A photo the customer sent should sit on the ticket. A tech who arrives without the cabinet photo will ask the same questions Jason already asked. That is how customers decide you do not listen.

Tone that survives a real shop

Short sentences. The fee. The window. The no. Humor is optional. Clarity is not. Jason should sound like your shop, not like a product demo.

He is bad at jobs you have not priced. He is bad at houses you have not mapped. He is bad at “just squeeze them in.” Those are human failures. Do not outsource them.

He is good at being awake. Use that.

Where he does not live

Jason does not live as a fifth tab on Team. Crews can get help. The desk brain lives in Hub and the web. If a tech needs the night ticket, they need Routes, not a chatbot.

Do not hide the orb in Settings. If the night desk is annoying to open, you will go back to giving out your personal number. That is how weekends die.

A 14-day Jason drill

Monday: visit fee. Tuesday: after hours rate. Wednesday: skip rule for a far house. Thursday: listen to one real transcript. Friday: change the sentence that caused a surprise. Week two: one real night call, one morning ticket on Team, one quote from the price book, one no that held.

If week two still has you answering the personal cell at 9pm, you trained a demo, not a desk.

Search phrases this page should earn

Jason AI Sqyre Hub, field service AI iPhone, after hours answering service HVAC, AI dispatcher plumbing. The honest product is a playbook plus an orb plus a Route in the morning. Canonical, FAQ, sitemap. Hub listing for the owner. Team listing for the stop.

The numbers on one job

A missed quote on the owner phone is not a small miss. It is a house that hired the shop that answered. Hub and Team exist so the yes, the clock, and the photo happen on the stop, not tonight on the couch.

quote

  • kind — visit

Walk the lead

walk

  • Open Hub — Confirm Jason is covering the desk before you leave the shop.
  • Tap the orb — Ask what is waiting: requests, quotes, unpaid.
  • Train one sentence — After hours rate, visit fee, and the next open morning.
  • Let him book the window — Approve big tickets if that is your rule.
  • Read Timeline in the morning — The night should already be tickets, not voicemail novels.

The picture

diagram

  • kind — route
  • title — Jason is the night desk
  • caption — The orb is how the owner stays the owner without sleeping next to the shop phone.
  • 9pm call — stop — Jason answers
  • Ticket — stop — Address, photos, window
  • Morning — stop — Owner reads Hub
  • Invented price — skip — Not allowed

The board

board

  • Playbook — The sentences Jason may say
  • Orb — Always on the Hub screen
  • Timeline — Night work becomes morning tickets
  • Limit — No invented discounts

Where Sqyre holds the work

Sqyre Hub is the owner app. Sqyre Team is the crew app. Jason repeats the shop sentence. Scheduling, payments, and the mobile app page are the web map of the same system.

Questions people ask

faq

  • Does Jason live in Sqyre Team? — Crews can get help. The desk brain lives in Hub and the web.
  • Will Jason invent a price? — Only if you never posted one. Put the fee in the playbook first.
  • Can I approve quotes first? — Yes. Stay in the loop on big tickets, or let him send.
  • Does he keep my number? — Yes. Customers call the shop line they already know.
  • What if I am in a basement? — Hub still holds the orb. Team holds the scan. Different jobs.

Before Friday

  1. Install the right app on the right phone.
  2. Run one real stop all the way to a photo or a payment.
  3. Delete the group text that used to be the board.

When you want the next piece, read Sqyre Hub on the App Store and Hub as the shop phone and The shop playbook.