Skip to main content
Every Azotha plan comes with direct email support from the Azotha team. Whether you have a question about your workspace, an agent produced something unexpected, or you want guidance on how to approach a new build, support is always available. The speed of that response — and the depth of technical guidance you receive — scales with your plan.

Support by Plan

The table below shows the support channel and guaranteed response time for each plan.
Response times are measured in business days from the moment you send your support request. Control and Autonomous requests are placed in a prioritized queue and handled before standard Core requests.

Dedicated Programmer Coach (Autonomous)

Autonomous plan customers receive something beyond reactive support: a dedicated senior programmer who is actively involved in your project throughout its lifetime. Your programmer coach reviews agent output before it is deployed, guides technical decisions as your software evolves, and ensures that the code Azotha builds meets quality and compliance standards before it reaches your customers or external users. This is not a helpdesk function — it is active technical partnership. Your programmer coach attends to the correctness, security, and architectural soundness of your software so that you can focus on describing what you need and leaving the technical assurance to an expert. If you are building software that will be used by people outside your organisation, the programmer coach is the layer of human oversight that gives you confidence before you go live.

What to Include in a Support Request

Providing the right context upfront helps the Azotha team resolve your issue as quickly as possible. When you send a support request, include the following:
1

Your workspace or project name

Include the name of the Azotha workspace or project the issue relates to, so the team can locate the correct environment immediately.
2

What you were trying to accomplish

Describe the goal in plain language — for example, “I was trying to add a customer login page to my portal” or “I asked the agent to connect the form to a spreadsheet.”
3

What the agent produced

Explain what actually happened. If there is an error message, copy it in full. If the output looks wrong, describe how.
4

What you expected instead

Tell the team what the correct result should have looked like, so they can reproduce and fix the gap.
5

Screenshots or your preview URL

Attach any screenshots that illustrate the issue, or include your preview URL so the team can inspect the live environment directly.

Getting Started vs. Ongoing Support

When you first join Azotha, your workspace setup and initial onboarding are guided by the Azotha team regardless of which plan you are on. You will receive clear instructions for accessing your workspace, submitting your first build request, and previewing your software — no technical background needed. Ongoing support covers everything that comes after onboarding: questions about how to direct the agents, unexpected behaviour in your workspace, guidance on expanding an existing project, and technical decisions about architecture or integrations. The more complex your software goals, the more value you will get from a Control or Autonomous plan — both of which include faster response times and, on Autonomous, the continuous involvement of your dedicated programmer coach.

Compare Plans

Review the full feature set for Core, Control, and Autonomous to find the right level of support and capability for your project.

Contact Azotha

Get in touch with the Azotha team to ask a question, discuss your goals, or raise a support request.