Never send passwords, one-time codes, invitation or reset links, session tokens, API keys, processor credentials, full card/bank data, database credentials, or an unredacted customer/payment screen. Support does not need those secrets to identify the account or reproduce a customer-visible workflow.
Before you beginRecord the exact screen, time, expected behavior, and smallest repeatable steps. Remove unnecessary customer and payment data from screenshots.
Step by step
- Start with the exact CentriPOS page and action. Write one sentence for what you expected and one for what actually happened, preserving the exact on-screen error text when it is safe. Distinguish a visible error from a loading state, missing control, incorrect result, or uncertain external transaction.
- Record the operating context before switching or refreshing: business name, location, register, open/closed register-session state, effective user role, device/browser or installed app, and the timestamp with time zone. Do not send internal tenant IDs unless support explicitly requests one through a secure channel.
- List the smallest repeatable steps from a known starting point. Include the exact control labels and whether the problem occurs every time, only for one record, one register/location, one role, one device, or one payment/integration provider. Mention any safe workaround already tested.
- Describe business impact and urgency factually: one user inconvenienced, a workflow blocked, multiple locations affected, customer waiting, register unable to sell, reporting discrepancy, or possible duplicate/uncertain payment. Choose Urgent only when immediate operational or financial risk genuinely requires it.
- Use a safe reference when it materially narrows the record: receipt/order/invoice number, customer code without unnecessary contact details, product SKU, purchase-order number, support ticket number, masked processor reference, or QBO document number. Never attach a full card number, bank account, password, token, or credential-bearing URL.
- Capture a screenshot only when it adds evidence. Crop to the CentriPOS page, include the relevant control/message and safe context label, and redact customer names, email, phone, street address, messages, signatures, balances, card details, credentials, QR/PIN codes, and unrelated browser tabs. Do not recreate or fabricate the screen when a safe capture is impossible.
- For CentriAI, choose the Sparkles Centri AI control → Support. Enter at least three useful characters, choose Normal, High, or Urgent, and choose Open support ticket once. CentriPOS includes the page/account context, current thread when present, plan, and effective email; record the returned ticket number/status and review Related knowledge.
- From this help center, open /support to email [email protected], call (614) 769-7619, or return to this checklist. An article’s Contact support link pre-fills the guide title in the email subject; still add the actual business/location/register and observed behavior.
- If emailing, use one descriptive subject such as CentriPOS support — [page] — [short symptom]. Put the context, expected/actual behavior, repeatable steps, impact, and safe references in the body. Send one clean request rather than separate fragments, and reply on the same thread with new evidence.
- For phone support, have the same context and safe reference ready. Never read a password, full card/bank number, OTP, API secret, or invitation/reset token aloud. If investigation must continue after the call, ask for or provide the ticket/thread reference so evidence stays together.
- For an uncertain payment, terminal timeout, duplicate-charge risk, register closure, deposit, QBO sync, or financial discrepancy, do not retry, void, refund, relink, close, or repair merely to create evidence. Preserve the current state and include amount, time, register, masked processor/QBO reference, and visible status so support can trace the full path safely.
- After submitting, keep the ticket/email reference and avoid changing the affected record unless normal business safety requires it. Add new timestamps, safe screenshots, or reproduction results to the same request. When resolved, verify the original workflow in the same business/location/register and confirm any financial or customer-facing result independently.
Screen and contract reference
| Control or area | What it means |
|---|---|
| CentriAI Support | In-product contextual ticket path that includes current page/account context and routes to the CentriPOS Support channel. |
| Normal | Routine question or issue without immediate material operational impact. |
| High | Significant workflow impairment needing prompt attention but without a stated immediate emergency. |
| Urgent | Immediate operational, customer, security, or financial risk; describe the concrete impact. |
| Ticket number and status | Primary reference returned after a successful in-app support request. |
| Related knowledge | Customer-facing help matches returned with the ticket for immediate self-service. |
| /support | Branded help-center contact page combining email, phone, and checklist paths. |
| [email protected] | Published CentriPOS product-support email. |
| (614) 769-7619 | Published Centri onboarding and product-support phone number. |
| Article Contact support | Email link prefilled with the current guide title; it does not automatically include operating context or reproduction details. |
| Operating context | Business, location, register, session state, effective role, device/browser, and timestamp with time zone. |
| Expected / actual | Short factual comparison of the intended result and observed result. |
| Reproduction steps | Smallest repeatable sequence using exact screen and control names. |
| Business impact | Specific staff, customer, location, selling, reporting, fulfillment, payment, or integration consequence. |
| Safe reference | Minimum non-secret identifier needed to locate the record. |
| Safe screenshot | Cropped/redacted evidence containing no unnecessary customer, payment, credential, PIN/QR, or unrelated browser information. |
| Uncertain financial event | State that must be investigated before retry, void, refund, close, relink, or repair to avoid compounding harm. |
| Same support thread | One ticket/email/call reference that keeps later evidence and resolution together. |
| No customer screenshot required | When privacy prevents a safe capture, send text context and a minimal safe identifier instead of exposing or fabricating an image. |
Expected result
The support request identifies the exact screen, time, business location, expected behavior, actual behavior, repeatable steps, and only the minimum safe record references needed to investigate.
Troubleshooting
- Capture the exact screen, time, expected result, and smallest repeatable steps.
- Remove unnecessary customer and payment information from screenshots.
- Include only safe receipt, order, or record references when contacting support.
CentriPOS API explorer · API Center administration
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.