Skip to main content

Documentation Index

Fetch the complete documentation index at: https://f4c7a9e2d8b1-docs.tenzo.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Rules Engine Overview

Admins may use the Rules Engine to customize interviews based on fields in the ATS. Rules follow the following pattern:
  • Conditions Conditions based on specified ATS fields to determine matching jobs
  • Actions How Tenzo should configure ATS jobs which match these conditions (eg. adding to a folder, interview generation instructions, specific setting configurations)

​
Rules for Generating the Interview Script

There are two distinct options for how the Tenzo interview script is created from an ATS Job.
  1. Script Auto-Generation Under this flow, a full set of screening questions will be generated based on the job description. This pathway is recommended for staffing agencies and recruiting teams which manage a large variety of jobs and there is not a standard screen through through which all candidates will be processed. Each screen can will then be automatically to the specific job requirements. Rule Action: Assign an AI Generation Template. Your organization can manage one default generation template standards to follow for inerview generation. You may also create additional rules to assign more specific generation templates when additional job conditions apply. Generation template rules stack meaning if multiple rules assign generation templates, all templates will be applied.
  2. Pre-Made Interview Template Under this flow, a premade interview template will be followed exactly for the newly linked job. This pathway is recommnded for teams with long-running jobs for which the interview questions and scoring will remain consistent over time. Rule Action: Assign a Job Template (a premade interview marked as a Template) as the action.

​
Rules for Restricting Job Syncs

It is easy to roll out the AI interview to only a specific set of jobs from your ATS. To restrict the interview to specified roles: For all rules which assign either a generation or job template: Specify any restriction conditions based on your ATS fields (eg. Location, Job Title, Industry, etc). To ensure all roles in your ATS are linked to an interview: You may specify a condtion-free Fallback Rule to assign either a Generation or Premade Job template. For all jobs not matching other conflicting interview creation rules, this fallback rule will apply and the interview will be created.

​
Rules for Background Templates

Background Templates are saved documents with supplementary information and rules to help the AI answer candidate questions during the interview and when communicating over SMS or email not available in the job description. Your organization has one default background template which will be assigned to all jobs automatically without any special rules needed. You may however also create rules to assign more specific background templates matching conditions. Example Use Cases:
  • Different teams in your organization have different polcies for which questions about the role the AI is permitted to answer. You may make a Separate Background info template for each team and a different rule for each.
  • If you would like to provide supplementary information (eg. an office phone number) that is different depending on the office.

​
Other Rule Actions

  • Assign a Folder
  • Assign Inteview Settings (eg. a specific calendar for follow-up interview)
  • Assign Question Constraints templates

​
Auto-Mapping: Automatic Rule Creation

​
What is Auto-Mapping?

Auto-mapping is a powerful extension of the rules engine that eliminates the need to manually create rules and templates for every unique value of a job field. Instead of creating individual rules for each department, client, location, or any other job attribute, you configure a single auto-mapping that automatically creates templates and rules for each unique value. When an auto-mapping is configured, the system automatically:
  1. Creates objects in Tenzo (background info, generation template, etc.) based on your naming pattern
  2. Creates an integration rule that assigns those objects to jobs with that value for the watched field
Auto-mapping configs appear as rows in the integration rules table. Expanding an auto-mapping row reveals the auto-generated child rules underneath. Each child rule is fully editable — you can customize any auto-created rule or template after it has been generated.

​
Key Concepts

  • Source Field — The job field to watch for unique values (e.g., “Department”) The same fields available in rule conditions are available here.
  • Naming Pattern — A template for naming created entities. Use {{value}} as a placeholder for the field value. For example, {{value}} Background Info becomes Engineering Background Info when the field value is “Engineering”.
  • Supported Actions — Auto-mapping currently supports the following action types: A single auto-mapping config can include multiple actions, creating several entities for each new value.

​
Creating an Auto-Mapping Config

  1. Navigate to Admin > ATS Integrations > Rules Engine
  2. Click Create auto-mapping in the rules table
  3. Fill in the configuration:
    • Config Name — A descriptive name for this auto-mapping (e.g., “Department Templates”)
    • Source Field — Select the job field to watch from the dropdown
    • Active — Leave this on to start processing new jobs immediately
  4. Add one or more actions. For each action, configure:
    • Action Type — Choose “Assign Background Template” or “Assign AI Generation Template”
    • Naming Pattern — Enter a pattern using {{value}} as a placeholder (e.g., {{value}} Background)
  5. Click Create Config
After creating the config, any future job syncs with new unique values for the selected field will automatically generate templates and rules.

​
Managing Auto-Mapping Configs

Viewing auto-created rules — Expand an auto-mapping row in the rules table to see all the child rules that have been generated. Each child rule shows the field value it was created for and the entities that were assigned. Editing a config — Click the edit icon to modify a config. Changes only affect future auto-creations. Existing rules and templates that were already created are preserved and unaffected. Deactivating a config — Toggle the Active switch to pause auto-creation without deleting the config. While inactive, new unique values encountered during job syncs will not trigger rule or template creation. Reactivating the config resumes processing for future syncs. Deleting a config — Deleting an auto-mapping config preserves all previously auto-created rules and templates. The rules become standalone and continue to function normally — they simply lose their association with the config.

​
Example: Auto-Mapping by Department

Consider an organization with 20 departments, each needing a unique background template with department-specific information. Without auto-mapping, an admin would need to:
  • Create 20 background templates (one per department)
  • Create 20 integration rules, each with a condition matching the department and an action assigning the correct template
  • Repeat this process every time a new department is added
With auto-mapping, the admin creates a single config:
  • Source Field: Department
  • Action: Assign Background Template with naming pattern {{value}} Background Info
On the next job sync, the system automatically creates a background template named “Engineering Background Info” and a rule that assigns it to jobs where Department equals “Engineering” — and does the same for every other department. When a new department appears in a future sync, it is handled automatically with no manual intervention.

​
Filling In Auto-Created Templates

Auto-created background info templates and AI generation templates are created blank — they have the correct name from your naming pattern but contain no content. After an auto-mapping creates new templates, you will need to navigate to the template and fill in the appropriate content. Auto-mapping handles the repetitive work of creating templates and wiring up rules, while you retain full control over the content of each template.