The KHOMP Settings Container: Per-Campaign KHOMP Options

If you run a KHOMP call progress gateway, you rarely want the exact same detection behavior on every campaign. A daytime B2C list and a careful B2B list answer differently, so the KHOMP Settings option lets you apply a specific set of KHOMP options to a single Campaign without changing anyone else. It is the per-campaign tuning knob for KHOMP-based answering machine detection (AMD (answering machine detection)) and call progress detection (CPD (call progress detection)).

What the KHOMP Settings field is

On the campaign detail screen, the KHOMP Settings field is a pull-down. It only shows containers that are the KHOMP_SETTINGS container type, so a generic settings container will not appear there. The default value is KHOMPSETTINGS, which is the baseline container shipped for the integration. Pick a different container from the menu when you want this campaign to behave differently from the rest.

This builds on the same idea VICIdial uses elsewhere with a Settings container: keep reusable groups of options in one named place, then point things at them. The KHOMP_SETTINGS type just scopes those options to the KHOMP gateway. Because the field reads the container type rather than the name, you cannot accidentally point a campaign at an unrelated container, which saves you from a whole class of confusing misconfigurations.

Think of it as a profile. One profile might be tuned to err toward calling something a machine, which protects agents from voicemail but risks treating a slow-to-answer human as a machine. Another might lean the other way to keep every possible live person, accepting that a few machines slip through to agents. The KHOMP Settings field is how you attach the right profile to the right Campaign instead of forcing one compromise across all of them.

How a campaign picks its container

flowchart TD
  A[Open campaign detail] --> B[KHOMP Settings pull-down]
  B --> C{Container type is KHOMP_SETTINGS}
  C -->|Yes| D[Appears in menu]
  C -->|No| E[Hidden from menu]
  D --> F[Select container for this campaign]
  F --> G[KHOMP applies these options to its calls]

Once selected, every call this campaign hands to the KHOMP gateway is analyzed using that container's options. Other campaigns keep whatever container they were assigned, so you can run tight detection on a sensitive list while leaving a high-volume list looser.

Setting it up cleanly

1. Create a new container with the KHOMP_SETTINGS container type, or copy the default KHOMPSETTINGS one.
2. Adjust the KHOMP options inside it with help from your system administrator.
3. Open the campaign and choose that container in the KHOMP Settings pull-down.
4. Run a small batch, then check the KHOMP Quick Stats Report and your status mix.

Naming matters here. Give each container a name that says what it is for, like a curfew-safe or aggressive-detection label, so the next person on the campaign does not guess. The choice you make in this field changes how machines, humans, and other outcomes land in each Status (lead status), so it is worth getting right before you scale the list. Always test on a small batch first. Pushing a fresh container straight onto a full list means any detection bias hits thousands of calls before you notice it in the numbers.

Keep a short note next to each container describing what you changed and why. KHOMP options are easy to forget six weeks later, and a one-line history saves you from re-deriving the same tuning every time a campaign underperforms. When you do change one, change one thing at a time and watch the result before the next adjustment.

Where this fits

The KHOMP Settings container only matters once the gateway itself is connected. If you have not done that yet, start with the KHOMP SIP gateway integration, and for the bigger picture on detection options read our AMD and CPD complete guide.

Want per-campaign detection tuning without learning every container type yourself? Our team sets up and maintains KHOMP options for each of your campaigns. See VICIfast pricing to get started.