Submit a support request
Include enough detail for us to reproduce or route the issue. We will reply by email.
Response priority
Urgency first, then impact.
Critical outages and customer-facing agent incidents move first. Routine changes follow the response window for the type of work affected.
General
Best effort
Account, access, billing, and bug reports. No guaranteed
change-work window.
Workspace
2 business days
Workspace, writeback, agent, and integration support during
business hours.
Customer-facing
1 business day
Priority handling for customer-facing agents, receptionist, and
approval routing.
Critical
As soon as possible
Site/app down, customer-facing agent incident, suspected data
exposure, or billing access lockout.
Critical right now? Mark the urgency as critical above and
email
support@webbuildr.io. Do
not submit secrets, passwords, API keys, payment card numbers, or
sensitive health/financial records in this form.
FAQ
Common support questions.
My agent gave a wrong or incomplete answer
Submit the exact prompt or customer scenario, what the agent
answered, and what the correct answer should have been. We use
that context to identify whether the issue is a missing source,
retrieval gap, prompt issue, or approval-routing problem.
How do billing and usage questions get handled?
Choose "Billing or usage question" and include the
workspace name plus the charge or usage window. We will review
your engagement terms, billing events, and relevant
usage records.
Can I request a new workflow here?
Yes. Use "Feature / change request" and describe the outcome,
sources, approvals, and handoffs. We will tell you whether it
fits your current scope of work or should be scoped as a new
engagement.
I found a security or privacy concern
Choose "Security/privacy concern" and avoid posting sensitive
secrets in the form. We will follow up by email with a safer
channel if we need logs, keys, or private records.