Contact Meetin.gs
Contact Meetin.gs about support, migration, partnerships, integrations, team scheduling, or a product workflow review.
Send a useful request
Include the public URL or event code, the action taken, the result you expected, and what happened instead. For team or integration questions, describe the hosts, meeting types, calendars, lifecycle messages, and systems that must stay authoritative.
- Missing times on a page? Check the missing times guide first.
- Email did not arrive? The delivery guide shows the log to read.
- Need a walkthrough for a team? Use the demo request instead.
Do not send sensitive data
Do not submit passwords, API keys, full payment details, private calendar content, or information that is not necessary to investigate the request. Use a test event when a safe reproduction is possible.
Response routing
Support issues are triaged by reproducibility and impact; partnerships and advanced workflow requests are reviewed against current product scope and the evidence needed for a testable release.
What happens after you submit
The request is stored with the name, email, message, and submission time. Product support is routed by reproducibility and impact. Workflow, integration, partnership, and demo requests are assessed against current scope and the evidence needed for a useful next step.
For a product problem
Include the public URL or event code, organizer action, participant action, expected result, actual result, time zone, and approximate time. A safe test event is more useful than copied private calendar content.
For a team or integration requirement
Name the authoritative system, trigger, fields, permissions, lifecycle states, fallback, owner, and rollout decision. State whether the requirement is mandatory now or can follow a test of the booking-and-polling core.
Contact questions
Can I request deletion or correction of personal information?
Yes. State the request and the email or scheduling context needed to locate the record. Identity verification and necessary legal or security retention may apply.
Where should I report a security concern?
Use this form with a safe description, affected URL, impact, and reproduction. Do not include secrets. Review the security reporting guidance.
How to use Contact Meetin.gs as an operating reference
Contact Meetin.gs about support, migration, partnerships, integrations, team scheduling, or a product workflow review. Begin with identify: Include the public URL or event code tied to the request. Then apply explain: State the action, expected result, and actual result in plain words. Finish with protect: Remove passwords, private calendar text, and unnecessary personal data.
Contact Meetin.gs in brief
Identify
Include the public URL or event code tied to the request.
Explain
State the action, expected result, and actual result in plain words.
Protect
Remove passwords, private calendar text, and unnecessary personal data.
Public product and editorial pages use stable slugs and distinguish the testable booking-and-polling core from advanced roadmap capabilities. That distinction is part of the site's product and content standard.
For any request, include only the context needed for the stated purpose. Clear identifiers, expected behavior, and lifecycle state are more useful than copied calendar content or sensitive free text. This keeps support, editorial references, legal questions, and security reports focused and safer to handle.
