- TENEKS does not show up in Claude
- In a Team or Enterprise organization, an owner decides which connectors members can use, so ask them to allow TENEKS. Otherwise, add it as a custom connector as shown above. The connection and the tools are the same.
- A question about a specific rep or call type comes back about everything
- Filters match your workspace’s own labels exactly, and a filter that matches nothing is reported. Ask Claude to describe your TENEKS workspace first. It comes back with the exact call-type and rep names that work.
- An answer is marked incomplete
- The answer could not be fully grounded in the underlying recordings. Narrow the question to a shorter period or a single rep and ask again. For an exact quotation, ask for the transcript.
- A connection that used to work has stopped
- Check the three conditions above first. Moving to another workspace permanently invalidates the existing token. In the Claude apps, disconnect TENEKS under Customize › Connectors and connect again, which takes you through the sign-in once more. In Claude Code, delete the old token in TENEKS, create a new one and run the setup command again.
- You lost the token
- It cannot be shown again. Delete it and create another. Deletion takes effect immediately, so it is also the right move if a token has ended up somewhere it should not be.