Support
What help looks like before there is a product.
Creobot opens in order, so there is no support queue, no status page and no ticketing. What exists is a direct line to the team building it.
Where to find answers today
The feature pages describe how each capability works and separate what is built from what is planned.
The glossary covers the terminology, including the terms vendors use loosely.
The blog goes deeper on retrieval, handoff, analytics and the decisions behind each.
Anything not covered goes to the contact page and reaches a person.
What support will look like as the rollout widens
Email support from the Starter plan and priority support from Pro, per the plan table. Those are intentions rather than contractual commitments, because there is no contract yet.
No response time target is published, and none will be until it can be staffed. An honest absence is better than a number that gets missed in the first busy week.
A status page arrives when there is a production service to report status for.
Questions
Ask on the contact page. Questions are answered by the people building the product rather than by a support queue.
Not yet. There is no public status page yet.
We do not publish one. An honest absence beats a target nobody is staffed to meet.
The feature pages describe how each capability works and mark what is planned. The glossary covers the terminology. Product documentation proper arrives with the product.
Email support from the Starter plan and priority support from Pro, per the plan table. Those are intentions rather than commitments, because there is no contract yet.
The team building it, which is a small team at Creoglyph. That is an advantage now and will not scale, which is why support tiers exist in the planned pricing.
Trust
Need an answer now?
Ask directly. Support is the team that wrote the thing, which is an advantage that will not survive scale.