Frequently Asked Questions

OUTAG3 takes reports for one location by phone and visitor chat. Completed phone cases arrive by email. Visitor-chat reports are emailed only after the visitor explicitly finishes the conversation.

The report includes the issue, assessed urgency, and captured details. A callback contact is included when supplied. Unclear cases are flagged for review.

For a live phone report, the caller number is retained with the case so your team can follow up. OUTAG3 does not place the callback or decide whether it is appropriate. The browser test does not include a caller number.

OUTAG3 summarizes the report and flags unclear details. Your team decides on refunds, callbacks, and other action.

Your team decides on refunds, callbacks, and on-site action. OUTAG3 prepares the report with context and urgency.

No. Day to day your team works with normal emails or tickets written in plain language about what happened. Nobody needs to write prompts or operate a special AI tool. Technical topics like webhooks or APIs mainly come up during setup and can be clarified in onboarding.

Typical cases fit well: money taken without product, product stuck in the chute, card payment failures or unclear age verification. Recurring reader or dispensing issues at one site map cleanly too. If your scenario does not match standard categories, we can tailor categories and rules to your operation.

Priority combines problem type and report content, for example how much revenue or customer satisfaction is at stake. That separates minor issues from real emergencies without your team rating every call manually. Especially important cases can be highlighted or marked for immediate handling.

Yes. You define how urgent each incident type is at each location, e.g. card reader outage as high and small amounts as normal priority. Rules can reflect your real operations and be refined after the pilot. Automatic triage then matches your internal escalation logic.

Yes. Categories, labels and mappings can match your machines, product groups and internal reporting. That also helps later analysis because reports land in your language, not generic defaults. Together with priority rules you get a picture that fits your business.

Whenever a case is unclear in content, touches sensitive topics or automatic classification seems uncertain, it is flagged for manual review. Your team then sees explicitly that human judgment is needed. That keeps quality high without hand-checking every small item.

The pilot lasts 60 days from first use, including AI assistance or visitor chat. 10 phone and test conversations of up to 2 minutes each provide up to 20 free minutes; short or interrupted conversations still count as 2 minutes. The shared pilot budget may pause further starts. Up to 20 organizations are approved. No card or automatic subscription.

Request a pilot place for your organization and one location. After approval, set up your workflow. Phone service starts after your business evidence and number are approved.

Further starts pause when the 60 days end or the shared pilot budget runs out. There is no automatic payment. Agree any continuation with OUTAG3.

The public demo is a sample, not a real customer case. In the pilot, test your own workflow. Test reports are available for 24 hours; conversations count toward the allowance.

Light and Starter are planned to provide the same case report quality. Starter is planned for up to five locations; Professional may add a dashboard, history, and SMS escalation. Paid plans are not available yet.

Your website request is saved for the OUTAG3 team to review. It is separate from reports submitted by your customers. Submitting the form does not activate access; we first review the organization request.

Phone reports are emailed. Visitor-chat reports are sent only after the visitor finishes the conversation. Replies are not processed; email, webhook, and CRM integrations are not available.

Yes. For operators with multiple brands, franchise structures or strict internal rules, separate storage per customer or tenant is supported. Configuration and data stay logically isolated. We align details with your requirements in the project.

We follow data minimization, purpose limitation and traceable processing, with controlled access to data. On request, retention periods can be defined per data type so you can meet deletion and documentation duties. Full detail is in our privacy policy.

Privacy-compliant use is generally possible when roles, retention and data processing agreements are set correctly and you meet your obligations as controller. OUTAG3 supports this with clear processes and configuration options but is not a substitute for legal advice. Involve your privacy specialist when in doubt.

Specific processing locations and subprocessors depend on the chosen infrastructure and connected partners, e.g. for hosting or telephony. Only data needed for intake, classification and handoff to you is processed. Regions and subprocessors are described in the privacy policy.

Lite case reports mark assessed urgency, with uncertain cases flagged for human review. SMS escalation is planned for Professional and is not available yet. Your team decides what action to take.

The Professional dashboard and case history are planned. The Lite pilot does not currently include a dashboard or recurring reports.

The pilot is limited to 20 manually approved organizations. Further starts are paused when the shared pilot budget is exhausted. No further free starts are available after the pilot expires or the allowance is used.

Lite starts at one location. The planned Starter tier covers up to five locations with the same case report quality and more voice minutes; Professional is planned for larger operations with dashboard and SMS control.

Lite does not include scheduled reports or a dashboard. The Professional dashboard and case history are planned. You can define which measures matter to your team and review the individual case reports.

OUTAG3 emails completed phone reports. Visitor-chat reports are emailed only after the visitor explicitly finishes the conversation; closing the chat does not send one. Replies are not processed; email, webhook and CRM integrations are not available yet.