Calendar
Turn Zendesk into a scheduling machine Join 1000+ organizations collectively already linking hundreds of thousands of calendar events to tickets each year, syncing seamlessly to and from Google and/or Microsoft, taking scheduling workflows to the next level! The Calendar app will help you to setup any workflow around events by allowing you to connect tickets to events or vice versa. For example, if your appointment booking system creates events in Google or Microsoft calendar then you can let the Calendar app take care of the rest by automatically creating tickets based off those events. Features Create any number of organization-wide calendars Agents can connect any number of personal calendars Granular calendar read and write permissions based on any combination of roles, groups or just specific users Google calendar integration Microsoft Outlook calendar integration Link events to tickets, link tickets to events Create events on tickets, create tickets on events Have events automatically created on tickets based on trigger conditions Have new tickets automatically created on new events from Google/Microsoft as they come in Optionally hide the full event details from Google or Microsoft and just show busy times Monthly, weekly and daily calendar views Calendar views allow for quick (re)scheduling based on availability Sync event data to ticket fields for use in ticket responses, views, triggers and reporting Workflows: generate ticket updates at any time before or after the event starts or ends Bundle pricing When you're ready to fully implement processes and workflow automation across your business, you can get all SweetHawk apps bundled in the SweetHawk Suite app. Check out our pricing calculator and see the how much value you can unlock with the Suite. We take data privacy very seriously, please see our privacy policy. About us Our Zendesk apps are used every day by over 500,000 Zendesk agents. These apps simplify and solve common and complex challenges, such as ITSM change management, Employee Service, and project management. Some of our most popular apps are: Tasks & Subtickets - automatically create task lists within Zendesk tickets or create subtickets to assign responsibilities out across multiple agents or teams Approve - create flexible and auditable approval processes for your Zendesk workflows (even if your approvers aren’t Zendesk users!) Calendar - link calendar events with Zendesk tickets to make your planning process simpler Recurring Tickets - set up repeating workflows (like renewals or security audits) once, then Zendesk will create tickets to manage those processes at any intervals you’d like. Multilingual Agent Experience — Supported languages: 🇧🇷🇵🇹 Portuguese, 🇩🇪 German, 🇳🇱 Dutch, 🇪🇸 Spanish, and 🇯🇵 Japanese.
Watari
Customer bugs, located in your code. Watari reads each Zendesk ticket you send it, including screenshots, screen recordings, PDFs, voice notes and logs, and turns it into a structured bug report: severity, steps to reproduce, impact, and the customer's own words. It then ranks the files and functions in your repository most likely to contain the defect, with the reasoning for each. A draft fix your engineers review. When it is confident enough, Watari opens a draft pull request on GitHub (or a pull request on Azure DevOps). Your reviewers and your own CI decide what ships. Watari never merges. Duplicate reports collapse into one bug. When five customers report the same regression, your engineers see one issue, filed in Jira, Linear, GitHub Issues or Azure Boards, with every ticket linked to it. Customers hear back when the fix is live. Watari drafts a plain-language root-cause update. After someone on your team approves it and the deploy is confirmed, it is posted to every Zendesk ticket that reported the bug, as a public reply or an internal note (your choice per update). Updates can be translated into each customer's language. How it works with Zendesk - You choose one or more Zendesk tags. Watari creates a webhook and a trigger in your account that forward tickets carrying any of those tags. Untagged tickets are never sent. - The only thing Watari writes to a ticket is the root-cause update your team approved. It does not change ticket status, tags or assignees. - Disconnecting removes the webhook and trigger it created. Also works with Intercom and Freshdesk for support, GitHub and Azure DevOps for code, Slack and Microsoft Teams for alerts. Pricing. You pay per Mapped Issue: a ticket Watari turns into a bug or feature request and maps to your code with high confidence. Draft pull requests, root-cause updates and issue-tracker sync are included. The 14-day trial includes 10 Mapped Issues and needs no card. Plans at https://watari.ai/pricing. Your data. Integration tokens are encrypted with AES-256-GCM, each workspace is isolated with row-level security, and your data never trains models. Our mapping accuracy, misses included, is public at https://watari.ai/proof. Data Watari accesses, and why - Reads: only tickets carrying your chosen tags: subject, description, public and internal comments, status, tags, attachments, names and emails of the requester, submitter and assignee, and the requester's organization name. - Why: to write the bug report, find the related code, group duplicates, and address the update to the right people. - Writes: only the update your team approves, as a comment on the reporting tickets. - Stores: in your Watari workspace (AWS us-east-1). Processed by the subprocessors at https://watari.ai/legal/subprocessors. Deleting your workspace deletes it after a 30-day grace period. Details: https://watari.ai/legal/privacy