Service → Requests is a service-focused communications inbox. It groups incoming activity into requests and shows workflow status such as Open, Responded, Estimated, Scheduled and Completed. New activity and a completed service request are separate signals; a fresh call can arrive on an older job.

Before you beginConfirm the active business, contact identity and approved communication channels. Review messages and recordings only when your role permits access, and keep customer addresses, phone numbers and private request details out of public screenshots.

Step by step

  1. Open Service → Requests and allow the configured providers to load. The business’s request-inbox settings determine which channels and providers appear; a channel’s absence does not establish that no request exists.
  2. Choose All, Open, Responded, Estimated, Scheduled or Completed, then use search for a name, phone number or meaningful request text. The displayed search is limited to up to 80 matching threads; clear filters before treating a missing result as a missing customer.
  3. Open the intended request and review its latest activity, time, channel and earlier messages. A New activity badge indicates unread activity and does not reset the request’s workflow stage. Pinned and unread threads can appear before other recent threads.
  4. Confirm the linked customer. Use the offered contact action to open or match the right record before starting work. Check email and phone ownership rather than choosing a similar name.
  5. Use Open job when a request already links to a job. Inspect that original job’s customer, estimate, visits and state before creating anything new.
  6. When the request belongs to an existing open job and Link to open job is offered, choose the exact eligible job for the same customer. The chooser excludes completed/closed work and jobs without the required service or financial context. Wait for Request linked to job and verify both records.
  7. Use Start job for genuinely new work. It opens the service estimate workflow with the available customer and request context. Review the scope, location, customer and pricing there; opening the workflow alone is not an accepted estimate, scheduled visit or payment.
  8. Use Continue in CRM only when offered for the connected provider, or call the shown customer number through an approved process. Review the actual recipient and channel before any outbound contact. A loaded recording is private service evidence, not public content.
  9. Use Mark read/unread and pin controls for inbox organization. If the latest activity is genuinely a separate request on an existing linked job, use Make latest activity a new request only after reviewing its scope and customer; this intentionally creates a new request bucket.
  10. Use Ignore request only when the business has decided no further request handling is needed. It removes the request from this service inbox’s normal results; it does not prove the underlying job was completed or that the customer received a reply.
  11. After linking, starting an estimate or changing request state, reopen the request and verify the correct job link and workflow badge. Record the next owner/action through the business’s service process.

Screen and contract reference

Control or areaWhat it means
Request workflow filtersAll, Open, Responded, Estimated, Scheduled and Completed.
New activityUnread activity indicator, separate from request workflow status.
Link to open jobLinks an eligible request to an eligible existing job for the same customer.
Start job / Open jobStarts an estimate for new work or opens the already linked job.
Continue in CRMProvider-specific continuation when an authorized CRM link exists.
Make latest activity a new requestSeparates new request activity from an existing linked request/job.
Ignore requestHides the request from normal service-inbox results; does not complete a job.

Expected result

The request is matched to the intended customer, linked to the correct existing or new job when needed, and left in a clear workflow/read state without creating duplicate work.

Troubleshooting

  • If activity is missing, clear filters, check the selected business, provider/channel settings and request-specific link before creating another request.
  • If no open jobs are offered, confirm the customer match and that the intended job is still open and has the required service/financial context.
  • If a provider sync or recording fails, keep the original request and capture safe time/channel/error evidence for support.
  • If a request was ignored unexpectedly, contact an authorized administrator with a safe request reference; do not create a duplicate to force it back into view.

More guides

Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.