The more context you give us up front, the faster we can fix your issue, hopefully in the first reply.
Include these in every request
A link to the affected meeting or page in Sybill (or the meeting title).
The date and time it happened, with your timezone.
The platform: Zoom, Teams, Google Meet, Webex, a dialer, desktop app, or mobile.
What you expected vs. what you saw.
A screenshot or screen recording if the issue is visual.
Issue-specific checklists
Recording didn't happen: was the meeting on your calendar? What are your joining preferences (Settings > My Meetings)? Was the notetaker admitted to the call?
CRM problems: which CRM, and an example deal or contact where the issue shows.
Email sync: the mailbox address and provider (Gmail or Outlook), and an example email that should have synced.
API / MCP: the exact error text (for example, "Public API is not enabled for this organization") and what you were calling.
Billing: the workspace name and the invoice or charge in question.
Reporting a bug
Please send it through the in-app chat or [email protected] with the details above. Our team reproduces the issue, files it with engineering, and keeps your ticket updated until it's resolved.
Requesting a feature
We love when our users tell us what can we do to make their lives easier, hence feature requests. They directly shape the roadmap. Tell us what you're trying to accomplish (not just the feature you'd like) so we can solve the underlying need as well. Watch 🚀 What's New in Sybill to see what ships.
Following up
Please reply in the same chat thread or email chain so the full history stays together.