For Phoenix Body Shops | Jüulio™

Key facts

• Dedicated campaign route: /for-phoenix-body-shops
• Primary CTA: Request a Quick Call -> /contact-sales with sourcePath preserved as /for-phoenix-body-shops
• Secondary CTA: Leave Your Info Instead -> route-local soft lead
• Phoenix soft-lead markers: sourceChannel=campaign-landing-page-modal and captureSurface=campaign-soft-lead
• Canonical brand line: Jüulio™ keeps the calls, the repairs, and the payments moving so the shop doesn't get backed up.
• This route is explicitly agent-readable and must appear in /agent/page and /api/public/agent/page

For Phoenix body shops

The customer's calling. Car's still in the bay. Payroll's still due.

• Jüulio™ keeps the calls, the repairs, and the payments moving so the shop doesn't get backed up.
• Want a quick call to see if this fits your shop?
• Keep customer updates from slipping, repairs from getting stuck, and payments moving before the shop gets backed up.

When the shop starts slipping, it never feels like just one problem.

The page frames the customer, the work, and the money as one operational pileup rather than separate issues.

• The customer: the update has to be real.
• The work: the car is still sitting there.
• The money: payroll still has to clear.

Keep the customer, the repair, and the payment from drifting apart.

The page positions Jüulio™ as the control layer that keeps front-office, repair, and payment handoffs from breaking apart.

• Keep the customer updated.
• Keep the repair moving.
• Keep the payment moving.

From the first call to the final payment, the shop stays tighter.

The operating-flow section explains how customer intake, repair progress, payment, and follow-up stay attached to the job.

• The customer reaches out.
• The repair starts moving.
• The invoice and payment get handled.
• Follow-up does not disappear.

Built for independent body shops where the day runs through a small front office.

The best-fit section is aimed at small independent Phoenix collision and body shops where the owner, manager, estimator, or front office is carrying the day.

• Best fit: independent collision and body shops, shops where the owner, manager, estimator, or front office is carrying the day, and teams that need customer updates, repair flow, and payment follow-through to stay connected.
• Probably not the right fit: dealership service departments, large multi-shop chains, general mechanic shops with a different day-to-day workflow, and businesses looking for generic small-business software.

Questions a shop will ask right away

The FAQ answers whether this is just payment software, whether the whole shop must adopt it immediately, and what happens after the first reach-out.

• Not just payment software.
• The whole shop does not have to roll out at once.
• A quick fit call comes before any deeper workflow conversation.

If this sounds like your shop, let's talk.

The page ends with the quick-call ask first and the lighter campaign soft-lead path second.

• Start with a quick call and we'll see if Jüulio™ fits the way your shop actually works.
• Not ready for a call yet? Leave your info and we'll follow up.

Allowed actions

Markdown mirror

# For Phoenix Body Shops | Jüulio™

Phoenix Touch 1 is a dedicated paid-search landing page for small independent Phoenix body shops carrying customer pressure, stalled repair pressure, and weekly cash pressure at the same time.

Human page: https://juulio.com/for-phoenix-body-shops
Path: /for-phoenix-body-shops
Locale: en-US
Schema version: 2026-04-06.agent-surface.v1
Content version: 2026-04-21

## Key facts
- Dedicated campaign route: /for-phoenix-body-shops
- Primary CTA: Request a Quick Call -> /contact-sales with sourcePath preserved as /for-phoenix-body-shops
- Secondary CTA: Leave Your Info Instead -> route-local soft lead
- Phoenix soft-lead markers: sourceChannel=campaign-landing-page-modal and captureSurface=campaign-soft-lead
- Canonical brand line: Jüulio™ keeps the calls, the repairs, and the payments moving so the shop doesn't get backed up.
- This route is explicitly agent-readable and must appear in /agent/page and /api/public/agent/page

## For Phoenix body shops
The customer's calling. Car's still in the bay. Payroll's still due.
- Jüulio™ keeps the calls, the repairs, and the payments moving so the shop doesn't get backed up.
- Want a quick call to see if this fits your shop?
- Keep customer updates from slipping, repairs from getting stuck, and payments moving before the shop gets backed up.

## When the shop starts slipping, it never feels like just one problem.
The page frames the customer, the work, and the money as one operational pileup rather than separate issues.
- The customer: the update has to be real.
- The work: the car is still sitting there.
- The money: payroll still has to clear.

## Keep the customer, the repair, and the payment from drifting apart.
The page positions Jüulio™ as the control layer that keeps front-office, repair, and payment handoffs from breaking apart.
- Keep the customer updated.
- Keep the repair moving.
- Keep the payment moving.

## From the first call to the final payment, the shop stays tighter.
The operating-flow section explains how customer intake, repair progress, payment, and follow-up stay attached to the job.
- The customer reaches out.
- The repair starts moving.
- The invoice and payment get handled.
- Follow-up does not disappear.

## Built for independent body shops where the day runs through a small front office.
The best-fit section is aimed at small independent Phoenix collision and body shops where the owner, manager, estimator, or front office is carrying the day.
- Best fit: independent collision and body shops, shops where the owner, manager, estimator, or front office is carrying the day, and teams that need customer updates, repair flow, and payment follow-through to stay connected.
- Probably not the right fit: dealership service departments, large multi-shop chains, general mechanic shops with a different day-to-day workflow, and businesses looking for generic small-business software.

## Questions a shop will ask right away
The FAQ answers whether this is just payment software, whether the whole shop must adopt it immediately, and what happens after the first reach-out.
- Not just payment software.
- The whole shop does not have to roll out at once.
- A quick fit call comes before any deeper workflow conversation.

## If this sounds like your shop, let's talk.
The page ends with the quick-call ask first and the lighter campaign soft-lead path second.
- Start with a quick call and we'll see if Jüulio™ fits the way your shop actually works.
- Not ready for a call yet? Leave your info and we'll follow up.

## Allowed actions
- `get_marketing_page_summary` (GET /api/public/agent/page) - Read a normalized summary for this Phoenix campaign page. Required fields: path.
- `get_contact_sales_context` (POST /api/public/agent/contact-sales/context) - Move from the Phoenix campaign page into the contact-sales action flow while preserving the Phoenix source path. Required fields: none.
- `get_homepage_soft_lead_context` (POST /api/public/agent/homepage-soft-lead/context) - Read eligibility for the Phoenix campaign's lightweight follow-up lane before opening or submitting it. Required fields: none.