Customer portal
Best for service-specific requests, invoices, backups, incidents and account history.
Open portal →Support with account context
Support that starts with the full account context.
Support, approved mockups, contracts, invoices, payment arrangements, backups and incidents stay connected to the client profile so the next step is clear.
Authenticated requests Service history Incident context Billing notes
Support queueEXAMPLE VIEW
3 activeTKWebsite change requestApproved mockup attached · Client profile matchedIn progress
EMEmail DNS verificationSPF and DKIM ready · MX pendingWaiting
BKRestore requestRestore point Aug 6 · 03:15 verifiedReady
Payment arrangements
Payment flexibility with a clear written schedule.
Arrangements are approved case by case. The CRM records the amount, installment schedule, next due date, grace period, reminders and notes so both sides can see the same terms.
Review account statusREMAINING BALANCE$320.00PAYMENTS4 × $80
01Payment receivedAug 1 · $80.00Complete
02Next paymentAug 15 · $80.00Upcoming
03ScheduledAug 29 · $80.00
04ScheduledSep 12 · $80.00
Common questions
Clear answers before you open a ticket.
Account-specific changes still require the authenticated portal and a recorded action.
Can AI change my service or billing?
No. The public AI helper cannot access accounts, charge customers, provision servers, restore backups or alter billing. Those actions require authenticated workflows and audit records.
Can I request a due-date extension?
Yes. Extensions and payment arrangements can be reviewed, but they are not automatic. Approved terms are recorded in the CRM.
How are outages handled?
Connected monitoring targets open incidents when checks fail and record recovery when the service returns. Customer notifications depend on the configured alert policy.
Do you keep my approved mockups?
Yes. The Mockups & Promises module stores versions, approval status and promised deliverables so both the client and the build workflow can reference the approved direction.