Frequently asked questions

The trial gives you 30 days and up to 100 session responses. You get full access to every feature — AI knowledge briefs, adaptive questioning, cross-session synthesis, Ask Mayetik, public questionnaires, multi-language support, and the template library. No credit card required.

You'll see an expired banner and won't be able to start new sessions. Your existing data — sessions, responses, and briefs — remains intact. Contact us to upgrade to Project Intelligence, Organizational Intelligence, or an Enterprise Intelligence rollout to continue.

Yes — email us at hello@mayetik.com and we'll find the right arrangement.

It depends on the session type. For private sessions sent via invitation, participants sign in with the same email the invitation was sent to — no separate registration step. For public questionnaires (shareable link), no account or sign-in is required; respondents answer directly in their browser.

Only Project Admins and Project Owners can view responses and briefs. Participants can only see their own brief. System Admins have access to all data on the platform. Participants cannot see each other's answers.

No. Voice recordings are transcribed immediately using OpenAI Whisper and then discarded — only the transcribed text is saved with the participant's answer. The audio file never touches Mayetik's database.

Yes — if you completed the session as a signed-in participant, Mayetik sends you an email ('Your knowledge brief is ready') with a link to view it once generation finishes, usually within 30 seconds of completing the session. If you responded to a public questionnaire without an account, the brief is shown on the completion screen but no email is sent.

Yes. Enable Public Questionnaire mode on any session to generate a shareable link. Anyone with the link can respond without creating an account or signing in. Responses are attributed to 'Anonymous' in the responses dashboard.

When a participant completes a session, Mayetik sends their answers to an AI model with a structured prompt that synthesizes themes, key insights, and recommendations into a readable prose document. The brief is generated automatically — no manual review step is needed before it appears.

GPT-4o-mini by default. You can configure a different model or a compatible API endpoint (such as Ollama or Azure OpenAI) via environment variables — useful if you want to keep data on-premises or use a different provider.

No. Mayetik is a structured form, not a conversational AI. Participants answer questions at their own pace; the AI's role is to synthesize their written or transcribed answers into a brief after completion. This keeps the experience predictable and the data structured enough to compare across participants.

Ask Mayetik indexes each completed brief as a semantic vector. When you submit a question, it's compared to the index, the most relevant briefs are retrieved, and the AI synthesizes an answer with citations linking back to individual sessions. It works at two scopes: project-level (searches one project's briefs) and org-level (searches across all projects in your organization, with an optional project filter). It requires the pgvector PostgreSQL extension, which is installed automatically on Railway production deployments.

The Knowledge Repository is an org-level page (Knowledge in the org dashboard) that shows every completed knowledge brief across all projects in your organization — searchable, filterable, and paginated. You can search across session titles and brief content, filter by project and date range, and jump directly to any brief or the project's Ask Mayetik interface. It gives org admins a single place to answer 'what has our team already learned?' without opening each project individually.

The Organizational Intelligence Dashboard (/orgs/[orgId]/intelligence, accessible from the 'Intelligence' button in the org header) gives org admins a live snapshot of knowledge capture activity. It shows four headline stats (all-time briefs, briefs in the last 30 days, completed sessions, and distinct contributors), a 12-week brief volume bar chart, a most-active-projects table, a top-contributors table, and the 6 most recently generated knowledge briefs. It also hosts the Theme Pulse — an AI analysis that extracts recurring themes from your most recent briefs.

Theme Pulse is an on-demand AI analysis on the Organizational Intelligence Dashboard. Click 'Generate' to analyse the 15 most recent completed briefs in your organization and extract 5–8 recurring themes — topics, concerns, or insights that appear across multiple contributors. Each theme shows a name, how many briefs reference it, and a brief summary. An overall observation captures the most striking meta-pattern. Re-run it any time to see how themes shift as new knowledge accumulates. Requires at least 2 completed briefs.

Org Synthesis generates an AI cross-project analysis across all project syntheses in your organization. It requires at least 2 completed project syntheses as input. Choose one of 6 focus types (Top themes, Client pain points, Operational risks, Lessons learned, Divergent views, or Market signals) before generating. The result synthesizes what all your project syntheses say through that lens, with source projects, a table of contents, DOCX download, brief pack download, and suggested next actions. Access it via 'Synthesize ✦' in the Knowledge Repository header.

Analysis Workbench generates source-backed themes from completed knowledge briefs, then lets admins inspect the evidence behind each theme. You can pin, dismiss, rename, annotate, copy an evidence pack, or jump into Ask Mayetik with a prefilled query. It is useful when you want to understand what the organization has collectively learned before creating a formal synthesis or strategy review.

The knowledge graph is Mayetik's structured layer over completed briefs. It extracts high-confidence people, decisions, risks, and commitments from brief content, then makes them browsable and filterable in the Knowledge Repository. Ask Mayetik source cards can also show entity badges so you can see important context before opening a source.

Session Studio is an AI assistant built into Mayetik that helps you design a complete session from a plain-language description. Describe your research goal, audience, and desired length in a chat message — Studio generates questions with types, hints, and branching logic. You can refine the design through follow-up messages before applying it to the session with one click. Studio is available on any session that is still in draft status (the Studio ✦ tab on the session detail page). Applying a Studio design replaces any existing questions, so review it carefully before confirming.

The Readiness Review is an AI-powered quality check you can run on any session before publishing. Open the session detail page and click the Readiness tab, then click Run readiness review. Mayetik scores the session from 0 to 100 across 8 design criteria — Audience Fit, Goal Coverage, Branch Logic, Low-Fit Detection, Summary Readiness, Admin Usefulness, Tone & Privacy, and Length & Friction — and returns a status (Ready, Needs edits, or High risk). The report includes a prioritized issues list with suggested fixes, and a set of suggested questions you can copy and add manually. The review is advisory only — it does not automatically edit the session or block publishing.

Mayetik can import SurveyJS-format JSON files, which it auto-detects and converts. For SurveyMonkey, Typeform, and Google Forms, you would need to export to SurveyJS format first — or recreate the session using Mayetik's template library or Session Studio (an AI-assisted question design tool).

16 types: Text, Short Text, Multiple Choice, Yes/No, Multi-Select, Rating Scale, Number, Slider, Date, Time, Email, Address (with optional USPS verification), Signature, File Upload, Location, and Ranking.

Yes — branch rules let you route participants to different follow-up questions depending on their answers. Conditions include equals, not equals, less than, greater than, contains, and is empty / not empty. You can also mark a question as terminal, which ends the session immediately when the participant reaches it.

The Mayetik Guide is a free AI advisor available on ChatGPT (no Mayetik account required). Describe your role, team, and goals and it recommends specific use cases and session types suited to your situation. It can also hand you off directly to Session Studio with your context pre-loaded. Find it linked from the Mayetik homepage, the template library, and the Content Intelligence page.

Categories classify the type of intelligence a session captures. Available categories are: Health Check, Win/Loss, Discovery, Alignment, Retrospective, Pre-Mortem, Stakeholder Feedback, and Other. Set a category on the session's Details tab — it appears as a badge in the session list and enables structural filtering across the knowledge base. Categories are optional and can be changed at any time.

A Series groups sessions that ask the same questions on a recurring schedule — monthly health checks, quarterly win-loss reviews, bi-annual alignment sessions. Create a series under Project → Series, give it a name and cadence, then assign individual sessions to it in each session's Details tab. The series detail page lists all instances side by side with synthesis status and response counts. Once at least two instances have completed syntheses, you can generate a trend analysis that identifies improving, declining, stable, emerging, and resolved themes across all instances.

Yes. Session responses export as CSV, project briefs export as JSON or CSV, and intake records export as CSV or JSON. Individual briefs can be downloaded as Markdown. Completed project and organization syntheses can be downloaded as DOCX, and synthesis brief packs bundle the synthesis, source list, Ask Mayetik prompt suggestions, generated follow-up questions, and suggested follow-up sessions.

Mayetik supports workflow integrations across CRMs, docs, notifications, task tracking, and automation. Current integrations include Slack notifications, Jira action-plan creation, Salesforce, HubSpot, and Dynamics 365 brief linking, Confluence and Notion page publishing, SharePoint and Google Drive synthesis publishing, and signed outbound webhooks for Zapier, Make, n8n, or custom HTTP endpoints.

Org admins can configure an outbound webhook in Settings. Mayetik sends a signed HTTP POST when a brief completes, a synthesis completes, or both. Payloads include an HMAC-SHA256 signature header so receiving systems can verify they came from Mayetik. This is useful for Zapier, Make, n8n, internal automation, or any system that accepts inbound webhooks.

Mayetik isn't a CRM — it's where the intelligence that feeds your CRM gets structured. When a session produces a knowledge brief, you can link that brief directly to any Salesforce opportunity, HubSpot deal, or Dynamics 365 account with one click. The brief appears as a note on the CRM record, visible to everyone with access, without leaving Mayetik. For teams that don't use a CRM, outbound webhooks let you push brief and synthesis events to any system — including Zapier or Make automations that route data wherever it needs to go.

A campaign is an org-level initiative that deploys one session across multiple departments simultaneously. You design the session once, add your departments, and Mayetik creates a separate project and session per department — cloning all questions and branch rules. You track completion across all departments from a single dashboard and can run a unified cross-department synthesis when responses are in.

Eight types: Retrospective (looking back at a completed cycle), Futurespective (commitments and risks for the coming cycle), After-Action Review / AAR (debrief of a specific completed initiative), Pre-mortem (risk identification before a major initiative begins), Lessons Learned (transferable knowledge at the end of a long project), Health Check (team morale, clarity, friction, and capacity), Alignment Check (whether teams share the same understanding of strategic priorities), and Win/Loss (analysis of a completed sales evaluation or competitive decision). Select the type when creating the campaign — it determines what the session is designed to learn. Retrospective and futurespective campaigns can be paired across cycles to enable cycle comparisons.

Separate projects require you to create each project, clone the session manually, manage invitations independently, and aggregate results yourself. A campaign automates all of that: one creation flow, bulk CSV participant import, per-department progress tracking, and AI-generated synthesis and action plans that read across all departments at once. Campaigns also support cycle management — clone for a new quarter, attach a cycle label, and (for retrospective and futurespective pairs) compare commitments against outcomes over time.

A cycle comparison compares what a team planned (captured in a futurespective campaign) against what they actually delivered (captured in a retrospective campaign). Once both campaigns have completed syntheses, click 'Compare cycles' on the retrospective campaign to generate a report showing where commitments were met, where they fell short, and patterns that repeat across cycles. Comparisons can be scoped to a department group.

Yes. On the campaign dashboard, use 'Import participants' and upload a CSV with three columns: name, email, and department. The department value must match the department name you set when creating the campaign (case-insensitive). Mayetik sends invitation emails to each address, skipping duplicates automatically. You can also send bulk reminders to anyone with a pending invitation or an in-progress session older than 24 hours.

Both work without a respondent account, but they serve different purposes. A Public Questionnaire is based on Mayetik's standard session flow — one structured question at a time with multiple choice, rating scale, and text fields. An Intake Form uses a conversational AI chat to collect a set of named data fields through free-form dialogue, then extracts the values automatically. Intake Forms are better for unstructured collection (e.g. 'tell me about your situation'); Public Questionnaires are better for structured surveys.

You define a list of fields when building the form — each with a label, a snake_case key, a type (text, email, date, etc.), and optional hints. The AI is given these fields as a schema and guides the conversation until all required fields are collected or the respondent indicates they don't have the information.

Yes. The form builder provides an embed snippet (an iframe) alongside the share URL. Paste it into any page. Respondents fill out the form without leaving your site.

Voice Call Intake is a phone-style respondent experience for intake forms. Respondents open a call link, hear a spoken greeting, answer questions by voice, review the transcript, and confirm each answer. Answers save field by field, so a dropped call does not lose all progress. It uses the same intake form and record as the chat interface; admins choose which link to share.

The extraction pass runs after every AI reply. If a value can't be confidently extracted, it remains missing and the AI will ask again in a natural way. The conversation ends when all required fields are collected — or the respondent gives up and closes the tab, in which case the record is marked 'incomplete' after 30 minutes of inactivity.

Yes. Enter a Webhook URL in the form's Settings tab. Mayetik will POST a signed JSON payload to that URL on each completion. The payload is signed with HMAC-SHA256 using your optional webhook secret — verify the signature on your server using the X-Mayetik-Signature header. Use 'Send test ping' to verify the endpoint before going live.

Yes. When a respondent completes an intake form, Mayetik automatically generates a prose summary of their responses and indexes it alongside session briefs. Completed intake records then appear as sources in Ask Mayetik queries — both at the project level and the org level — attributed as 'Form: [form name]' with a blue badge to distinguish them from session briefs. No additional configuration is needed; indexing happens automatically on completion.