In AIS (AI Integration Suite), every Pre-Trained Assistant (PTA) operates based on two foundational instruction layers: Company DNA and Employer Expectations. These layers define how a PTA communicates, behaves, and interprets its role within a specific organization.
They are essential to ensuring that each PTA is both context-aware and organization-aligned, without introducing conflicts or ambiguity in its actions.
Company DNA
Company DNA is a shared, organization-wide definition of the business’s culture, tone, and general communication style
Purpose
- Create consistency across all PTAs in the same AIS instance.
- Define how the company expresses itself—formality, tone, values, and communication preferences.
Applies to
- All PTAs hired by the business.
- Serves as a non-instructional, informational layer that influences tone and interpretation.
Examples of what it includes:
- “Our tone is friendly, but professional.”
- “We use British English spelling.”
- “Avoid hard-sell language in customer interactions.”
- “When referring to customers, use their first names, not ‘sir/madam’.”
Configuration
- Set by the client (employer) in the Client Portal.
- Written once and applied universally across that business’s AIS instance.
Employer Expectations
Employer Expectations are specific, instructional guidelines for how an individual PTA should behave and respond in its assigned role.
Purpose
-
Provide task- and context-specific instructions tailored to the assistant’s function.
-
Control how the PTA makes decisions, prioritizes actions, and manages edge cases.
Applies to
-
Each PTA individually.
-
Acts as a directive layer, guiding functional behavior.
Examples of what it includes:
-
“The Sales Support PTA should follow up on open leads after 48 hours if no response is received.”
-
“Escalate technical questions that are not in the knowledge file to the human IT team.”
-
“If a customer uses the phrase ‘cancel my order,’ initiate the cancellation process immediately.”
Configuration
-
Set by the client via the Client Portal, per PTA.
-
Updated independently based on evolving job roles or business logic.
Why Keep Them Separate?
Clear Separation Ensures
- No instruction conflicts—Company DNA sets the overall style; Employer Expectations guide specific actions.
- Scalability—As businesses grow and add more PTAs, the shared DNA remains intact, while expectations can vary by role.
- Safety and predictability—System behavior is more transparent, traceable, and easier to audit or adjust.
This layered approach allows PTAs to sound and act like part of the same company, while still performing very different tasks in very different ways.
Summary Table
| Aspect | Company DNA | Employer Expectations |
|---|---|---|
| Scope | All PTAs in the organization | Individual PTA |
| Purpose | Define tone, values, communication style | Set task-specific instructions |
| Instructional? | No | Yes |
| Editable by | Client (via Client Portal) | Client (per PTA) |
| Update Frequency | Occasional | Role-dependent |
| Conflict Risk | None | Isolated (per PTA) |
| Role in Behavior | Influences how PTAs sound | Controls what PTAs do |
This dual-layer design is one of AIS’s key architectural safeguards, allowing clients to fine-tune their AI workforce without risking miscommunication, misalignment, or system-wide behavioral issues.
