Interface.ai

voice/anti-ai.md

---
bcp_version: "1.1.1"
file_type: anti_ai
parent: https://registry.brandcontextprotocol.dev/interface-ai-c4f5e1a8/.well-known/brand.md
last_updated: 2026-09-24
---

# Anti-AI voice guardrails

Apply these patterns in addition to general editorial review. They are inferred from the public homepage and have not been confirmed by interface.ai.

No qualifying live external community pattern list is declared. Under the spec fallback, use `brand_additions` alone. These are Encoded's draft example patterns, not interface.ai-approved rules.

```yaml
brand_additions:
  - pattern: "In today's rapidly evolving banking landscape"
    type: opener
    rationale: "Generic scene-setting delays the credit union, community bank, or member job."
  - pattern: "revolutionize banking"
    type: phrase
    rationale: "The site names specific agent surfaces. Novelty language is weaker than the surface and the job."
  - pattern: "seamless banking experience"
    type: phrase
    rationale: "The homepage integration line uses this kind of filler. Name the core, CRM, or payment connection instead."
  - pattern: "not just a chatbot, but a bank"
    type: structure
    rationale: "A predictable contrast, and it misstates the company. interface.ai is not a bank."
  - pattern: "zero hallucinations"
    type: claim
    rationale: "The hiring line says there is no room for hallucination. That is a standard, not a measured guarantee."
  - pattern: "guaranteed call automation"
    type: claim
    rationale: "Customer quotations on the homepage are institution-specific. Do not promote them to a promise."
  - pattern: "industry's first"
    type: phrase
    rationale: "The meta description says this about BankGPT. Keep it as a sourced comparative claim or leave it out."
  - pattern: "em dash used as a sentence hinge"
    type: punctuation
    rationale: "The live site uses this hinge. This demonstration uses a full stop or a colon so the claim stays easy to check."
  - pattern: "From answers to autonomy"
    type: structure
    rationale: "Broad range constructions hide which surface does which job."
  - pattern: "The future of community banking is here"
    type: closer
    rationale: "End on the surface, the member moment, or the dated source."
```

## Structural checks

- Do not open with an abstract statement about AI when a contact-center or member job is available.
- Do not call interface.ai a bank, a credit union, or a core processor.
- Do not merge voice, chat, collections, employee AI, and Nexus into one capability sentence.
- Do not convert a homepage statistic into an evergreen fact.
- Do not convert one institution's quotation into an average result.
- Do not describe fraud checks or biometric verification as frictionless or unbeatable.
- Do not give a member financial, credit, tax, or legal advice.
- Do not use an em dash as a hinge in new demonstration copy.