Object and record-level instructions
Teach Ally to understand your custom data architecture
Because your CRM relies on custom structures, Ally needs to understand what each specific data table represents. Object-level instructions act as a blueprint. If you ask Ally to update a record, it uses these instructions to know exactly what fields are required and how they should be formatted.
1Define the entity
Explicitly explain what the custom object represents, for example a Person, a Deal, an Invoice, or a Project.
2Establish field validation rules
Teach Ally what type of information belongs in each of your custom columns. This prevents it from putting the wrong kind of data in the wrong place.
3Enforce clean execution
When Ally analyzes data or fills in blanks, it references these instructions to keep your database structure clean. Tell it how records should be formatted, what to highlight in summaries, and what counts as a complete record.
Example object instruction
Continuing the same company, here is how they described their Enterprise Deals object:
This object represents active sales opportunities. The Deal Value column must always be estimated in USD. The Technical Requirements column is a custom text field that must only contain bulleted lists of the client's current software stack. When summarizing a Deal record, always highlight the key technical blockers and the primary decision-maker.
Next: give Ally rules for specific groups and views.