Group and view-level instructions
Optimize Ally for localized, specific workflows
Group-level instructions are the most granular tier of context. They control how Ally behaves inside a specific filtered view or pipeline stage. This gives Ally the localized rules it needs to help you clean data, move records, or handle immediate operational tasks without breaking your workflow.
1Set entry criteria
Instruct Ally on what specific types of records qualify to be in this group. This helps it understand why a record is here and what stage it is at.
2Automate data evaluation
Ally can look at a record, cross-reference your group rules, and tell you exactly what is missing to progress a deal to the next stage.
3Unlock contextual actions
If you ask Ally to draft a follow-up email from within a specific group, it will use the group's rules to know exactly what the email should be about, without you having to explain the situation from scratch.
Example group instruction
Inside the Enterprise Deals object, this team has a filtered group for deals undergoing technical compliance checks:
Deals in this view are currently being reviewed by the client's IT security team. To move out of this group, a Deal must have a completed SOC2 Sent date column. If I ask you to draft an email to a contact in this view, the email must exclusively focus on checking the status of the security questionnaire and offering to connect their CTO with our Head of Engineering.
The three layers work together. Ally knows your company, understands your data, and follows the rules of wherever it is being used. That combination is what makes it genuinely useful instead of just fast.
Next: put these ideas into practice with the Allyos playbooks.