On this page

Jump to any section using the links below

Hubhus supports multiple ways to route and assign leads automatically.
Assignments can be based on postal codes, select values, source, status, visit behavior, and many other criteria — depending on your workflow.

This article explains the assignment features that Hubhus actually provides:

• User-level auto-assignment rules

• Positive and negative lists

• Assignment conditions (advanced filters)

• Assignment weights and load balancing

• Booking form assignment

• Calendar-based assignment

• Automation fallback rules

1. User-level auto-assignment rules (core method)

Every user can have their own assignment rules inside the campaign.
These rules define when a lead should be assigned to this person.

You find these rules under:

Campaign → Users → Auto-assignment

You can assign based on:

• Postal codes

• Text fields

• Select-field values

• Specific field values

• Ranges (e.g. 1000–2000)

• Multiple conditions

Example from your screenshot:

Field: Post nr.
Positive list:

1000–2000

➡ Leads with postal codes between 1000 and 2000 are assigned to this person.

2. Positive list & Negative list

Positive list

Leads must match one of these values to be assigned.

You can enter:

• individual values

• semicolon-separated values

• intervals (e.g., 3000–4000)

• newline-separated values

Negative list

Leads excluded from assignment, even if they match the rest of the rules.

This is ideal for:

• specific blocked areas

• special cases

• premium regions assigned to another salesperson

3. “Assign this person when no other people are matched”

This checkbox makes the user a fallback assignee if:

• no other user’s rules match

• no other user receives the lead through assignment logic

This is often used for:

• support inbox

• admin catch-all

• overflow fallback

4. More auto-assign filter options (advanced rules)

Users can have detailed filtering criteria that determine whether a lead may be assigned to them.

From your screenshots, advanced conditions include:

Hubhus ID requirements

• specific IDs only

• exclude specific IDs

Created requirements

• time window

• origin

Follow-up requirements

• must or must not have follow-up

Status requirements

• must be in specific statuses

• must NOT be in specific statuses

• check for status history

• check who set the status

Assigned person requirements

• must be unassigned

• or must NOT be assigned to specific users

Field value requirements

• must have certain fields filled

• must have files uploaded

• must NOT have files uploaded

Web page visit requirements

• visited/not visited specific pages

Automation history requirements

• must have triggered a specific automation

• must NOT have triggered any of a list

Email requirements

• email sent/not sent

• email opened/not opened

Unsubscribe & blacklist requirements

• subscription rules

• blacklist whitelist rules

Calendar requirements

• must/must not have an event

Custom logic

Use conditional logic:

@if(%lead_postal_code% == 2000){1}@endif

This makes assignment extremely customizable.

5. Assignment weights (load balancing)

When multiple users match the assignment rules, Hubhus decides based on assignment weight.

From your screenshot:

How weights work

• The user with the highest weight wins the assignment

• Weight 0 means “not assignable”

• Empty weight uses default logic

• You can calculate weights dynamically using conditions

Examples

Fixed weight:

12

Not assignable on Mondays:

@if(<hh-date.format input="now" output="N"/> == 1){0}@endif

Limit number of leads per person:

@if(<hh-data.leads.count filter-assignee="id=3252" filter-assignee="set_at>now -7 days"/> > 10){0}@endif

This allows you to:

• reduce workload on busy users

• implement fair distribution

• implement rotation based on time windows

• block assignment during holidays or time off

6. Assign from booking forms

Booking forms can assign the booked resource automatically to the lead.

Booking form option:

“Assign booked person to lead”

When enabled:

• the calendar resource chosen in the booking

• becomes the assigned person on the lead

This is ideal for:

• inspections

• meetings

• home visits

• consultant assignments

7. Assign via Calendar → Sync assigned person to resource

In Calendar → Settings → Calendar View, you can enable:

Sync assigned person to calendar resource

This means:

• Moving an event from Resource A to Resource B

• Automatically updates the lead’s assigned person to Resource B

Useful for:

• rescheduling

• dispatching

• replacing consultants

• last-minute routing changes

8. Using automations as fallback assignment

If the lead remains unassigned after X time, an automation can step in.

Example: Assign lead after 1 hour

Trigger: Lead created (delay 60 minutes)
Condition: assigned_person is empty
Action: set assigned_person = <user>

Automations are useful for:

• escalation

• queue management

• SLA handling

• catch-missed assignments

Best practices

• Use positive lists for clear regional ownership

• Use negative lists to exclude special cases

• Use assignment weights to balance workload

• Enable booking-form assignment when meetings determine ownership

• Use calendar sync for operational workflows

• Always test assignment rules with sample leads

• When in doubt, check the assignment history on the lead

Learning outcome

You now understand how to configure:

• dynamic user assignment rules

• positive/negative routing lists

• advanced filtering for assignment eligibility

• assignment weighting

• booking-form-based assignment

• calendar-based assignment

• automation-based fallback assignment

? Common searches

lead management • lead tracking • customer management

? Also known as

customer • contact • prospect

Related articles

Configuring search settings
How do I filter leads by specific criteria?
How do I give API access to a specific campaign?
How do I set up a new campaign?
How do I share a direct link for customer self-registration?