Provider OS
Lesson 5 / 12
Customers and Requests
A plain-language path for reading demand, checking fit, and keeping customer context close.
Use requests and customer memory to decide what deserves follow-up and what needs clearer information first.
Why this matters
Good providers do not answer every request blindly. They check scope, service fit, timing, location, and customer context before promising work.
What this feature is
Requests show incoming demand, while customer memory helps the provider avoid repeated questions and keep context together.
Safe to use now
- Read requests, customer context, service fit, timing, and location before promising work.
- Use customer memory inside approved HubbCentral screens.
Provider example
A cleaning provider receives a quote request, reads the room count, timing, and location, then checks whether it fits the published services before replying.
What to click next
- Open Requests for new demand.
- Open Clients when you need customer memory.
- Open Quotes when the request is ready for a written estimate.
What not to do yet
- Do not promise a job before checking scope and schedule.
- Do not export customer lists or copy private details outside approved workflows.
- Do not use automated outreach unless a future approved send path exists.
Short video
Lesson focus
Workspace cue
Demand to customer memory
Requests show incoming opportunity. Customer memory keeps details and history from disappearing between conversations.
Key highlights
- Read the request before replying.
- Use customer context to avoid repeated questions.
- Move toward quotes only when the request is clear enough.
Before you start
- Know which services you actually offer today.
- Be ready to say no or ask for clarity when a request is not a fit.
- Keep customer details private and inside approved HubbCentral screens.
Step by step
- Open Requests from Provider OS.
- Read the request scope, timing, location, and customer notes.
- Check whether it matches your published services and availability.
- Open customer context when you need history or contact details.
- Move toward a quote only when the next step is clear.
Ready to apply
- You can find requests.
- You can explain why one request is a good fit or not.
- You know when to open customer memory.
If you get stuck
- If a request is unclear, ask for the missing detail before quoting.
- If the customer context is thin, stay with the facts visible in the request.
What success looks like
You can triage requests without rushing into bad-fit promises.
Quick checklist
- Open Requests.
- Pick one request and identify scope, timing, and fit.
- Open customer memory if more context is needed.
Practice it in the live product
The lesson stays public, but the CTA routes directly into the live HubbCentral surface tied to this workflow.