FAQs

Common questions about Trigz.

Quick answers for teams evaluating, setting up, or troubleshooting Trigz workflows.

Getting started

What should we automate first?

Start with one repeated workflow that has clear ownership, approved knowledge, and a measurable outcome.

Do we need a technical team to start?

Many first workflows can start from templates. Integrations, APIs, and advanced actions may need technical review.

Can we start from a template?

Yes. Templates help teams avoid a blank setup and begin with a proven workflow pattern.

What knowledge can Trigz use?

Trigz workflows can be configured around approved content such as FAQs, documents, product data, policies, and internal guides.

When should a human take over?

Use handoff for sensitive, complex, high-value, low-confidence, or missing-knowledge cases.

Should we add all content at once?

No. Start with clean approved sources, test common cases, then expand knowledge based on gaps.

Where should support requests go?

Use the support intake page for setup, account, billing, product, or troubleshooting questions.

Should I include private data in forms?

No. Do not include passwords, API keys, credentials, payment details, or private customer data in public forms.

Where are legal and privacy resources?

Use the Trust Center, Privacy Policy, Terms of Service, and legal/privacy contact path.