I want to build something
Share the project type, audience, expected outcome, and any screenshots or examples that show what good looks like.
Answers to common thinQit questions, plus where to go for product, billing, security, privacy, and teammate workflow support.
Use this page when you need a quick answer or the right next place to go. Name the task, the product area, and whether the issue is product, account, privacy, or security related so it reaches the right path faster.
Yes. Include the audience, pages or screens, style direction, integrations, and acceptance criteria so the first version is easier to review.
Yes. Documentation works best when it captures the decision, the context behind it, related links, and what should happen next.
Start in the billing settings inside the product. For contract or vendor-pack questions, use the legal contact listed on the company and terms pages.
Use security@thinqit.io, which is listed in the public Terms of Service for security disclosures.
Open the teammate workspace and check the Settings or Provisioning tab first. Most setup issues come from missing target details, permissions, connected tools, or unclear first-task boundaries.
Use the Team settings page to invite people, review seats, and manage workspace access. AI teammates are managed from the Teammates workspace.
Include the workspace, product area, what you were trying to do, what happened instead, and any relevant screenshot or error text. Do not send secrets, passwords, or private tokens by email.
Use legal@thinqit.io for contracts, DPAs, vendor packs, and terms questions.
Use privacy@thinqit.io for privacy rights and data requests.
Most support questions become easier once the job is clear. Name the task, the product area, and whether you need product help, account help, or a sensitive contact route.
Share the project type, audience, expected outcome, and any screenshots or examples that show what good looks like.
Share the page, decision, research note, or launch context that needs to become easier for the team to find later.
Share the role, permissions, success criteria, escalation path, and the first task that needs ownership.
Support happens through in-product help, Mason-style sessions, account settings, and clear escalation paths when a human should step in.
Support can happen through in-product help, Mason-style sessions, knowledge-base articles, and the right escalation path when a person needs to step in.
For billing, team members, notifications, and integrations, the fastest answer is usually inside workspace settings.
Security, privacy, and legal questions need clear routing. Product support, account help, and sensitive disclosures should not all go through the same path.
Each teammate has a clear role. Use Cody for implementation, Sophia for SEO and GEO, Jessica for security, Mason for support, and other teammates for planning, QA, operations, or legal work.
The public website lists separate contacts for general questions, legal/vendor pack requests, privacy rights, and security disclosures. Keep sensitive account details inside the product whenever possible.