Ask what matters. Remember what was agreed.
Use your services, pricing and the customer’s history. Collect only the missing essentials, keep promises visible and bring the next useful step to the team.
PRIVATE BETA · BUILT FOR SERVICE BUSINESSES
More booked work.
Less busywork.
Your leads, conversations, and jobs. One workspace.
AI helps with the next step. You stay in control.
Built by a service-business operator.
Set up with you, around the way you work.
Calls & messagesConnected channels. AI assistance.
bazas.aiEstimates & invoicesAI drafts. You review.
Mileage & ETAiPhone trips in closed testing.
Receipts & expensesCollected for your review.
Trusted referralsAgree a partner workflow.
One customer. The next step stays connected.
CRM + AI ASSISTANCE + HUMAN CONTROL
Bring the conversation together.
CallsTextEmailWebsiteMarketplace leads
01 / THE WORKFLOW
A lead is just
the beginning.
The useful part is knowing what happens next. Explore an illustrative workflow, from the first message to a reviewed response and a shared job record.
01 / 03
The message arrives.
Keep the request and the customer together, even when your team is busy.
bazas.aiILLUSTRATIVE EXAMPLEJL
Jordan Lee
New enquiryIncoming call
Sample names, messages, and screens illustrate the workflow. Features and integrations in your pilot are confirmed during setup.
Your AI dispatcher
Keep the whole job moving.
From the first enquiry to the final follow-up. Bazas connects the conversation, the work and the next decision — so your team can focus on the customer.
Rollout in progress
We are implementing this connected dispatcher experience. Start with an agreed pilot; expand automation as each workflow is checked with your company.
Choose how much to delegate
You review. You decide.
You stay in charge. AI follows the conversation, spots missing details and prepares the next step. Reviewing a suggestion does not send a message or change a booking.
1Enquiry2Agreed scope3Visit4Invoice5Confirmed payment6Aftercare
Illustrative workflow · rollout scope
A new channel. The same conversation.
A marketplace enquiry can continue by SMS or email without losing its context. We are connecting source-specific rules, email threads and human handoff across supported channels.
Plan the visit around the real work.
Coordinate suitable technicians, availability, job duration and travel. Handle changes and cancellations, and alert a person when a decision or response is missing.
Turn agreement into clear documents.
Connect preliminary estimates, customer approval, attachments, additional work and the invoice. Keep the accepted scope visible instead of asking your team to enter it again.
Follow the payment. Not just the message.
A customer saying “paid” is not confirmed funds. Connect verified or manually recorded payments, balances and receipts; update reminders when the situation changes.
Stay helpful after the job.
Build a clear path for feedback, complaints and warranty questions. Keep service follow-up separate from marketing, and stop when there is no useful next action.
The right context for the next decision.
Five connected layers shape the dispatcher we are building. A company’s rules and a customer’s needs belong in the same decision.
- PlatformPermissions and action limits
- CompanyYour team and business rules
- ServiceScope, questions and pricing
- SourceThe rules for this enquiry
- RequestThe customer and what was agreed
Start with the scenario that fits your business
The rollout includes human-only work with optional AI suggestions, first replies, collecting details, consultation and estimates, booking for approval, automatic booking and an agreed full workflow. Custom combinations keep your approval points and individual pauses.
FROM ENQUIRY TO AGREED WORK
A clear estimate.
A customer who knows what comes next.
One customer context connects the estimate, agreed work and customer documents. Explore the steps and see local product previews with fictional data.
Pilot with setupAI drafts. People decide.
Start with the scope. Let AI help with the draft.
Pilot can prepare an estimate from the job context. Your team checks the scope, prices and recipient before sending the customer a link.
Your team reviews and sends
A preliminary range can be refined after an inspection.
Discuss this workflow
The previews use fictional data and inactive controls. The interface shown is in English; website languages and document languages differ. Confirm the workflow with us during setup.
02 / THE WORKSPACE
Everything connected.
A clearer next step.
Keep the conversation close to the work. Start with the workflow your business needs most, then build from there.
01One conversation.
One conversation.
Context for the next step.
Customer details, supported incoming messages and the next action stay together. Authorized team members see the available context behind the request.
AI that knows
your business.
Services, policies, and customer context help shape a useful draft. Review it, edit it, or take over.
From enquiry
to organised work.
Keep jobs, scheduling, estimates, and invoice details connected. Confirm the workflows in scope before your team relies on them.
04At the desk.
At the desk.
Out in the field.
Use the invited web workspace for the office workflow. An iPhone companion is in TestFlight testing for selected field tasks; access and build scope are confirmed separately.
Discuss your setupIntegrations and automation depend on your accounts, permissions, and agreed pilot setup. See what we check together
BUILT AROUND REAL WORK
More of the working day.
In one place.
The enquiry is only the beginning. Keep the conversation, the field work and the paperwork connected—with AI helping at the steps you review.
MILEAGE JOURNAL
Internal testingMake work travel count.
Automatic iPhone trip recording is in closed testing. Review the collected routes and classify business or personal travel. We check recording and a real PDF or CSV export in the agreed pilot.
EXAMPLE WORKFLOW
Review trip → classify → export
Detailed trips are visible to the person who made them.
AI RECEIPT CAPTURE
Pilot with setupA photo. Less paperwork.
AI reads the store, date, totals, tax and line items from a receipt. Check the result, correct it and link the purchase to a customer or job.
EXAMPLE WORKFLOW
Receipt photo → fields → your review
Expenses and supporting documents collected for your review.
TAX & BOOKKEEPING
Pilot with setupKeep the numbers connected.
Review income, expenses and supporting records. QuickBooks invoice and payment sync, supported Plaid bank imports and selected exports are separate connections to check for your workflow.
CONNECTED WORKFLOWS
QuickBooks · Plaid · selected CSV exports
Confirm tax settings and records with your accountant. Bazas does not file taxes.
AI ESTIMATES & INVOICES
Pilot with setupFrom job details to a draft.
Ask Pilot to prepare an estimate or invoice with line items, prices and agreed job context. Review the preview, confirm the draft and send it as a separate step.
EXAMPLE PROMPT
“Draft an invoice from the accepted estimate.”
Keep the accepted version, attachments, payment stages and separately approved additional work together.
PILOT & REMINDERS
Pilot with setupTurn a request into the next step.
Ask Pilot to prepare a reply, payment reminder or visit reminder. Check the recipient, message and channel before confirming a supported action. Manage scheduled messages and internal next steps.
EXAMPLE PROMPT
“Schedule a payment reminder for tomorrow at 9.”
Pilot review and separately enabled customer automation have different controls.
CUSTOMER INBOX & EMAIL AI
Pilot with setupPick up where you left off.
Keep conversations from connected channels in the customer context. AI helps summarize and draft replies. Business email is connected with founder assistance; each company’s mailbox and delivery route need their own setup.
EXAMPLE PROMPT
“What did we promise, and what needs a reply?”
Private Gmail receipt import is a separate, read-only connection.
VOICE RECEPTIONIST
Pilot with setupTake enquiries while you work.
An AI receptionist can take enquiries on a configured business line. Check calendar booking and transfer to a person during working hours together. New after-hours handling and browser calling are separate releases.
EXAMPLE WORKFLOW
Enquiry → availability → booking or handoff
Available call notes and recordings follow provider settings and staff permissions.
JOB LOCATIONS & ETA
Pilot with setupHead to the right place.
Keep the service address attached to the job. Mark yourself on the way and request a driving ETA; available Google Maps traffic data improves the estimate.
EXAMPLE WORKFLOW
Confirmed address → route → arrival estimate
An ETA is an estimate; automatic arrival messages need separate acceptance.
CUSTOMER PORTAL
Pilot with setupA next step your customer can see.
Share a company-branded place for customer projects, documents and contact with the team. Access is by link, with available actions and access recovery checked during pilot setup.
EXAMPLE WORKFLOW
Shared link → intended documents → contact the team
Website translations and document languages may differ.
A CLEAR START, A VISIBLE NEXT STEP
Availability follows the accepted workflow.
Reviewed
Start with one useful workflow.
Choose the supported channels and documents your team needs. We confirm the account connections, access and result before relying on the workflow.
- Connected inboxPilot with setup
- Estimates and invoicesPilot with setup
- Customer portalPilot with setup
Check the field workflow together.
Selected iPhone tasks and automatic trips are being tested. The available build, device access and accepted scope are confirmed separately.
- iPhone companionInternal testing
- Automatic trip recordingInternal testing
See what comes next.
These releases have their own acceptance steps. They are not included automatically when you join a pilot.
- Browser calls for dispatchersIn development
- New after-hours handlingIn development
- Built-in card checkoutPlanned
- Self-service onboardingPlanned
Availability changes as workflows are accepted for release. Your pilot agreement defines the scope, costs, support and review controls for your company.
YOUR NETWORK, IN THE WORKFLOW
Keep the relationship.
Share the work.
A full calendar or a job outside your scope can still become useful work. Agree a focused pilot for sharing work with trusted providers. Assignment, access, conversations and commission terms are checked separately.
FOR SERVICE TEAMS
A full calendar. A trusted handoff.
Discuss an overflow or specialist job with a trusted provider. Agree the assignment and what customer context can be shared, then follow the permitted work history.
FOR REFERRAL OPERATORS & SMALL AGENCIES
Bring the lead. Coordinate the work.
Bring customer relationships and a trusted contractor network. Test a limited workflow for assigning work, following permitted conversations and recording agreed commercial terms. A shared multi-company dispatcher and automatic payouts are separate milestones.
Discuss your workflowTRUSTED PARTNER NETWORKPilot with setupSend workReceive work
- 01
Offer the work
Agree the service, area and information that can be shared.
Confirm the sharing rules - 02
Choose the partner
Confirm the assignment and the provider’s access to the customer context.
Access follows the assignment - 03
Keep one thread
Check the permitted shared conversation and the author of each reply.
A shared record of the work - 04
Keep terms visible
Agree percentage or fixed commercial terms for the selected workflow. Recording terms does not move money.
Clear commission terms
Make more of your network.
Find a path for overflow and specialist work without rebuilding the customer story in another chat.
Keep the handoff accountable.
Agree who can see the shared work and which actions remain visible to the originating company.
Agree on the economics early.
Agree the terms before handing off work, then confirm the result separately from settlement.
03 / HUMAN CONTROL
A capable assistant.
Your call.
Begin with reviewed drafts and a focused workflow. Agree your service boundaries, timing, costs, and handoff rules before enabling customer-facing automation.
How we handle your data THE OWNER STAYS IN THE LOOP
01
Review
Read and edit the proposed reply.
02
Take over
Handle the conversations that need you.
03
Set boundaries
Agree what automation can do before it goes live.
04 / BUILT FROM THE FIELD
Made by someone
who does the work.
Bazas grew out of running Repair ASAP. The goal is practical: less time chasing messages and details, more time doing the work customers called for.
Nikita
Founder & Builder
THE EARLY CUSTOMER EXPERIENCE
Start with the part of your day that needs to work better.
A conversation. A focused pilot. Real feedback.
Apply → Discuss fit → Agree the scope → Get invited
05 / BEFORE YOU JOIN
A few things
to know.
Private beta means a considered start. Clear expectations before your first day.
Pilot terms and plan referencesHow do I get access?
Apply with your company and the workflow you want to improve. Nikita reviews the fit, walks through your lead flow, and agrees on a pilot scope before creating or inviting you into a workspace.
Who is the private beta for?
Small service businesses and contractors in the U.S., starting with New York City. We also discuss focused pilots with referral operators and small agencies. We check your services, team, channels and must-have workflow together.
Will AI send messages or book jobs automatically?
Start with reviewed drafts. Customer-facing automation is enabled only for agreed channels after setup and testing. Pricing, service boundaries, recipients and human handoff are reviewed with you. New after-hours and dispatcher calling workflows are separate releases.
Which integrations are supported?
We check your accounts, permissions, and provider limitations before setup. SMS, email, voice, website, Yelp, Thumbtack, and calendar workflows can require founder assistance. Listing a channel does not guarantee that every account or workflow is supported.
Can I use Bazas on iPhone?
The web workspace is available by invitation. An iPhone companion is being tested through TestFlight and is not publicly available on the App Store. Access, the supported build, and the field workflows available are confirmed separately before onboarding.
Is the pilot free?
Access, duration, limits and subscription or external AI, SMS and call costs are agreed before setup. An individually agreed free pilot may be possible. Applying does not create an account or start a subscription.
Can I bring my existing data?
We discuss your import, export, and staff access requirements before onboarding. Available formats and export scope depend on the workflow. Start with one useful process and agree a migration plan before moving more records.
How do I get help?
Use the Support page or email support@bazas.ai. Include your company, the affected workflow, and what happened. Please leave out passwords and API keys. We agree the support arrangements during onboarding.
LET’S TALK ABOUT YOUR BUSINESS
Your next chapter.
Start small.
Tell us what you do and what you want to make easier. Nikita will review the fit and discuss a practical pilot with you.
Access is by invitation. Pilot scope, duration, limits, and costs are agreed before setup. Applying does not start a subscription.
Prefer email? hello@bazas.ai