Skip to content
Team Forms Team Forms Docs

Use the AI assistant

Open Ask AI from the bottom-right corner of Team Forms. The assistant can:

  • answer questions using the Team Forms documentation;
  • create a new form;
  • update custom CSS;
  • patch or replace a form schema;
  • inspect existing data sources and representative live/preview items before configuring a form field;
  • prepare a submission email template for review;
  • add or update calculated values, conditions, and other form logic;
  • send a bug report or feature request to Team Forms support.

You can attach images and documents with the paperclip button, paste copied images, or drag files onto the open assistant. PNG, JPEG, WebP, GIF, and SVG images can also be inserted into a form when they fit the embedded-image limit. Conversations are retained by OpenAI and can be reopened from the conversation menu.

Creating and editing forms

Section titled “Creating and editing forms”

Describe the outcome and the information the form should collect. By default, the assistant creates a polished starting point with a relevant form icon, a replaceable sample logo, introductory guidance, logical sections, responsive field layouts, and the correct submit or wizard navigation. Ask for a plain, minimal, or unbranded form if you do not want those presentation defaults.

The assistant will not add advanced integrations, workflows, permissions, or data collection unless you request them and provide the required context.

For an existing form, open it in the builder before asking for a change. The assistant reads a compact copy of the latest draft before editing it and preserves unrelated schema properties and embedded assets. Focused requests are applied as small patches; broader rebuilds may replace the schema.

Changes run directly in your browser and appear in the builder’s undo history. Review the result in Preview, and use undo if you want to revert it.

Submission email templates are handled differently: the assistant drafts a readable plain-text message by default, populates the unsaved fields, and opens the Email tab. It uses HTML only where useful, such as links or tables, and does not save, enable, authenticate, or send anything. Preview the email and select Apply manually if you want to keep it.

The assistant is available only to users who can build forms. Form-editing tools also require the relevant form and builder context to be open.

Styling and form logic

Section titled “Styling and form logic”

When updating custom CSS, the assistant inspects sanitized versions of both the browser form and generated PDF markup. Tell it whether a style should apply everywhere, only in dark mode, or only to the PDF. Team Forms keeps the configured font family consistent because PDF rendering supports a restricted set of fonts.

When adding JavaScript-based calculations, validation, conditions, or actions, identify the target field and describe the behaviour. The assistant loads the declarations for that exact component and setting before changing the schema, which gives it the available values and output variable for that context.

For exact component types, property names, nested layouts, validation rules, and executable settings, see the Form schema API reference. In particular, the builder’s Calculated Value setting is stored in the calculateValue schema property.

Conversations are handled by OpenAI’s Responses API. Team Forms does not persist assistant transcripts in Cosmos DB.