CentriAI receives the active tenant, page path and label, location, and register when available. It can answer with live or knowledge-backed context, but a response is not authorization to change customer, inventory, payment, accounting, or register data. Actions that require confirmation are presented as review controls. Never put passwords, card data, tokens, or unnecessary customer information into a prompt or ticket.

Before you beginSign in with the Centri Account established from your personal invitation, then confirm the intended business before continuing. Individual invitation and password guides explain the identity options available on those exact screens.

Step by step

  1. Choose the Sparkles Centri AI control in the operating-context bar. On mobile it opens as a bottom sheet; on larger screens it opens from the right. The header states the current page label, such as Sell, Market Intelligence, Engage, Sales, Products, Inventory, Admin, or Dashboard.
  2. Choose Ask for a question. Use a rotating page-specific suggestion or enter your own prompt. CentriPOS sends the question with the current tenant, location, register, page path and label, local time zone, and the current day’s UTC boundaries to the answer service.
  3. Wait while Checking live CentriPOS data… is shown. Read the answer and inspect Sources used when present. Verify dates, scope, customer identity, receipt, register, location, and totals against the underlying CentriPOS screen before acting.
  4. If an answer returns a pending action requiring confirmation, use its review control rather than assuming the action already occurred. Current review routes can open location/register selection, Sell, Products, a matching customer profile, or a report. Multiple matching customers are presented separately.
  5. Use the clock/history button to open up to 12 recent conversations for the current tenant and effective user. Pinned threads sort first. Choose a thread to continue it, use the Star to pin or unpin, or choose New to avoid adding unrelated context to an older thread.
  6. If Saved conversations are not available yet or This conversation could not be saved yet appears, a local response can still be visible, but do not assume it will survive refresh. If the answer request fails, CentriAI states that no POS action was performed and offers retry or support.
  7. Choose Help for product guidance. Related knowledge can link back to customer-facing articles on support.centripos.com. Use the article itself for the maintained step-by-step procedure and exact screenshot boundary.
  8. Choose Support when a person needs to investigate. Describe what happened using at least three trimmed characters, select Normal, High, or Urgent based on real business impact, and choose Open support ticket once.
  9. The ticket request includes the active tenant, current thread when present, a first-line summary capped at 200 characters, full description, priority, page context, public plan name, and effective profile email. On success, record the Ticket number and status. It is saved in CentriPOS and routed to the CentriPOS Support channel.
  10. Open any Related knowledge links supplied with the ticket result. If ticket creation fails, copy the safe description and use [email protected] or (614) 769-7619 from the support site. Include page, context, time zone, expected and actual result, repeatable steps, impact, and only a safe record reference.

Screen and contract reference

Control or areaWhat it means
Centri AI / SparklesExact in-product launcher in the operating-context bar.
Page-aware headerNames the supported product area from which CentriAI was opened.
AskQuestion-and-answer mode using current page and operating context.
Prompt suggestionsRotating page-specific starting questions.
Checking live CentriPOS data…Answer request is still running.
Sources usedReturned evidence labels, optional details, and counts supporting the response.
Pending actionStructured proposal requiring confirmation and opening a review destination; it is not proof that an operation already happened.
Matching customersSeparate identity choices when a profile request has multiple matches.
Conversation historyUp to 12 tenant/user-scoped recent threads with pinned items ordered first.
StarPins or unpins a saved conversation.
NewStarts a draft thread without adding to the open conversation.
Persistence warningSaved thread or message storage is unavailable or failed; local content may not survive refresh.
HelpProduct-guidance mode connected to published knowledge paths.
SupportContextual ticket mode inside CentriAI.
Support noteAt least three trimmed characters; the first line becomes a summary limited to 200 characters.
Normal / High / UrgentUser-selected ticket priority based on business impact.
Open support ticketSends the tenant, thread, description, priority, page/account context, plan, and effective email.
Ticket number and statusConfirmation that the request was saved and routed to the CentriPOS Support channel.
Related knowledgeHelp-center matches returned with the created ticket.
[email protected]Published human email fallback.
(614) 769-7619Published Centri support phone number.
No exact screenshotThe approved Amelia Grant Harbor & Hearth manifest contains no safe final-state CentriAI drawer, so this guide uses no invented image.

Expected result

This workflow is complete only after CentriPOS reflects the intended result. Final checkpoint: Open any Related knowledge links supplied with the ticket result. If ticket creation fails, copy the safe description and use [email protected] or (614) 769-7619 from the support site. Include page, context, time zone, expected and actual result, repeatable steps, impact, and only a safe record reference.

Troubleshooting

  • Use the newest invitation or password-reset link; older links may no longer be valid.
  • Confirm the email address matches the account your administrator invited.
  • If a business or location is missing, ask an administrator to review your role and access.

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.