1
Always assign new tickets to the person who reported them unless a specific assignee is mentioned
2
Our product is a B2B SaaS billing platform. “Invoices” always refer to customer-facing invoices, not internal finance docs
3
When creating bug tickets, always set priority to High and issue type to Bug
SaveReset
How it works
You write plain-language instructions that tell Janet how to handle this project. Every time Janet processes a request — creating tickets, triaging, responding to messages, running automations — it reads your instructions first and follows them. Instructions apply project-wide across all interactions.Set-up
Click the Gear icon in the header of your Project Board to access Project Settings, select the Configure tab, then select Custom Instructions.Acme Project
ACMECustom Instructions
Add instructions that Janet will follow for this project on every call.
1
Always assign new tickets to the person who reported them
2
Our product is a B2B SaaS billing platform
3
When creating bug tickets, always set priority to High
Examples
Good custom instructions are specific and actionable. Here are some ideas:Interpreting requests
Interpreting requests
Control how Janet interprets ambiguous requests and what it assumes by default.
- “Always assume a request is asking to create a new ticket unless an existing ticket is explicitly referenced.”
- “If a message could be a question or a ticket, treat it as a ticket.”
- “If I ask you to remind me about something, I want you to schedule a ticket for 6AM PST that day.”
Product context
Product context
Tell Janet what your product does, who your users are, and any domain-specific terminology. This helps Janet write better ticket descriptions and make smarter triage decisions.
- “Our product is a developer tools platform. ‘Workspace’ means a team environment, not a physical office.”
- “We have three user tiers: Free, Pro, and Enterprise. Tier-related tickets should always be tagged with the tier name.”
Field defaults
Field defaults
Set rules for how Janet should populate ticket fields when creating or updating tickets.
- “Default all new tickets to the Backlog column unless the request says otherwise.”
- “Always set priority to High for anything mentioning data loss, security, or downtime.”
- “Assign infrastructure tickets to @alice and frontend tickets to @bob.”