Login

u/Ok-Constant-9143

r/UseApolloIo r/Zendesk
▲ 7 r/Zendesk

Organizing Zendesk KBs for Human vs. AI Agents: Unified or Separate?

Hi everyone,

I’m curious how folks are organizing their Zendesk knowledge bases when balancing human agents and AI agents.

Much of the advice around deploying AI agents suggests that the knowledge you expose them to directly dictates their scope and response quality. If AI knowledge needs to be tightly controlled to ensure accuracy, does it make more sense operationally to maintain a single, permissioned KB or split them up?

For those who are already down the path of deploying AI agents, what setup has worked best for you?

  • Unified KB: Sharing one KB across human and AI agents, restricting what the AI sees via permissions or labels?
  • Dedicated KB: Creating a separate knowledge base tailored specifically for AI consumption?

Would love to hear how you’re managing this!

reddit.com
u/Ok-Constant-9143 — 14 days ago
▲ 2 r/UseApolloIo

Confused by Apollo’s lookalike domain advice

Hello, we are just getting started with Apollo. I’m confused by Apollo’s lookalike domain advice.

They recommend:

  1. Don’t forward the lookalike domain to your main site.
  2. Don’t put links to your main domain in outbound emails.
  3. If you publish a landing page on the lookalike domain, don’t link from that page to your main site either.

I get the deliverability logic, but how does this work in practice?

If a real prospect gets an email from a lookalike domain, they’re probably going to want to check out the company before replying. If there’s no link to the main website anywhere, doesn’t that make the email feel less legit?

Curious, how are people handling this?

u/Ok-Constant-9143 — 3 months ago