Skip to main content
GullySystem
Business Services · Outbound Sales Centre Management Software

Campaigns, calling lists, call outcomes, caller targets and incentives in one place.

Manage an outbound sales centre in one system. Campaigns hold their scripts and targets, list batches are loaded, cleaned against suppression lists and split among teams, and every attempt ends in an agreed outcome. Callbacks, sales, client acceptance and each caller’s incentive follow from the same entries, so the floor and the client read one set of figures.

  • Campaigns, outcome codes and incentive slabs entered as your plan states them
  • Past list batches and caller records migrated
  • Edits to outcomes and slabs handled by GullySystem staff when asked

In-house teams and agencies that dial for client brands both work in this system, which GullySystem configures around their campaigns. Campaign managers, callers, team leaders, quality listeners and client managers use it. Each list record carries its attempts and outcome, each sale carries the client’s acceptance, and incentives follow the accepted sales.

Where it breaks today

What goes wrong before the software.

Attempt counts live in a dialler export

Which numbers were tried, how often and by which team is read from a file. Records get called twice in a day or never called at all.

Suppression lists are filtered by spreadsheet

Numbers that opted out or were excluded by the client are removed by hand before each load. A single missed filter reaches a caller.

Outcome codes mean different things per team

Interested, pending and callback are used loosely. Conversion rates for two teams on one campaign cannot be compared.

Callbacks depend on a caller’s notebook

A promised time sits on a sticky note or in a personal diary. When the caller is absent, the prospect is not called.

Client rejections arrive after the call is forgotten

A delivered sale comes back for a missing detail. The caller, the recording and the campaign take effort to find.

Incentive slabs are applied on a month-end sheet

Callers wait to learn what they earned. Clawbacks for rejected sales are matched by hand against earlier payments.

How it runs

How the work flows through it, step by step.

  1. 1

    Campaign setup

    The manager creates the campaign with script, calling hours, outcome codes, target and assigned teams, and links it to the client.

  2. 2

    List loading

    A batch is uploaded, duplicates are dropped, suppressed numbers are removed, and the remainder is split among callers with a set number of attempts.

  3. 3

    Calling

    Callers work their list and pick an outcome after each attempt. Sales capture the details the client requires, and callbacks get a time.

  4. 4

    Quality listening

    Listeners sample recordings against the script and any consent wording set for the campaign, and note results against the caller.

  5. 5

    Client acceptance

    Sales are delivered to the client. Accepted or rejected status returns with a reason, and rejected sales go back to the caller’s team leader.

  6. 6

    Incentive and review

    Accepted sales feed each caller’s slab. Team leaders review rates, and the client receives its campaign report.

Modules

What is inside.

Every module can be switched on, left out or changed to match how your team already works.

Campaign set-up

Create a campaign with its client, script, calling hours, outcome codes, sales target and assigned teams.

List batches and attempt rules

Load batches, remove duplicates, set the number of attempts and gaps, and see the share of each batch already worked.

Suppression and consent lists

Hold numbers that must not be called, with source and date, and match every new batch before callers receive it.

List split among callers

Divide a batch by team and caller, rebalance when someone is absent, and keep a record of who held each record.

Outcomes and callbacks

Use one agreed outcome set for every attempt, book callbacks with a time, and show callers the next one due.

Script and offer library

Keep the current script, rebuttal notes and offer terms for each campaign, with the date a revision took effect.

Sales and client acceptance

Capture each sale with the details the client needs, then record its acceptance or rejection and the reason.

Appointments for field reps

Book meetings for the client’s field representatives with time and address, and mark whether the visit took place.

Call quality review

Sample recordings, score them on script wording and consent lines, and keep results against the caller for coaching.

Caller targets and incentive slabs

Set targets, apply slabs and clawbacks for rejected sales, and show each caller a running figure for the month.

Shifts and attendance

Plan shifts by campaign, record logins and breaks, and show how many callers are working each list.

Client campaign reports

Report records worked, contacts made, sales, acceptance and rejection reasons per campaign for the client.

Solutions inside

The business modules it is built from.

Each one is also available on its own, or inside a system built for you.

  • Lead Management

    Each batch record shows its attempts, gaps and holder, so no number is dialled twice in a day or left untouched.

  • Data Migration and Import

    Batches arrive as files, duplicates are dropped, and the clean remainder is divided between teams and callers with a record of who held each row.

  • Pipeline Management

    Interested, callback and sale sit as stages on one agreed set, so conversion between teams is counted the same way.

  • WhatsApp, SMS and Email Notifications

    A promised callback raises a reminder for the owner, and moves to the team leader when the time passes without a call.

  • Commission and Incentives

    Accepted sales feed each caller’s slab, rejected ones apply the clawback, and the running figure is visible all month.

  • Attendance & Time Tracking

    Logins and breaks are recorded by campaign, so a leader sees how many callers are working each list at any hour.

  • Dashboards and KPIs

    Records worked, contact rate, sales and rejection reasons roll up per campaign for the client’s period report.

  • Audit Trail

    Every addition to or removal from the suppression list keeps who made it, when, and the source file it came from.

Services

How we would put it in.

Setup, data migration, integrations and anything built on top.

Who uses it

One system, each person sees their part.

For campaign managers

Set up campaigns, load and clean list batches, assign teams, and watch each batch against its target.

For callers

See your next records and callbacks, pick the outcome for each attempt, and follow your running incentive figure.

For team leaders

Read contact and conversion rates through the shift, move callers between campaigns, and handle rejected sales.

For quality listeners

Sample recordings, score script and consent wording, and send results to the caller’s team leader.

For client managers

Review the campaign report, acceptance and rejection reasons, and agree changes to the script or list.

Reports

The numbers the owner asks for.

  • Records worked, reached and converted by batch
  • Attempts per record and gaps between them
  • Callbacks promised against callbacks made
  • Sales accepted and rejected by reason
  • Conversion by caller, team and campaign
  • Incentive earned and clawed back by caller
  • Suppression matches removed per batch
Good fit

Who this is built for.

  • Telesales centres selling products or services by phone
  • Outsourced outbound centres running campaigns for several clients
  • Appointment-setting teams for field sales forces
  • Collections and renewals outreach teams
  • Lead qualification centres feeding a sales team
  • Multi-site centres with callers in more than one country
Honest answer

When it is not the right choice.

  • A sales team of a few people dialling from a shared sheet can keep working in the sheet.
  • A centre that only needs a dialler to place calls will find its dialler provider covers that need.
Made to fit

Adapted to your business before it goes live.

You are not handed a login and left to it. The product is set up around your records, your people and the tools you already use.

Outcome codes and attempt rules

Outcome names and attempts per record follow the way your campaigns already sort a call.

Incentive plans

Slabs, thresholds and clawbacks for rejected sales are entered as your plan states them, per campaign if they differ.

Suppression sources

Do-not-call lists, client exclusions and any registry file your advisers require are imported before each batch, in a layout we settle with you.

Lists and callers migrated

Past batches, callback diaries and caller records arrive from your dialler exports and sheets.

Hosting and changes

GullySystem hosts the system for all sites. Call scripts, outcome lists and incentive slabs are revised by GullySystem staff whenever your campaign managers ask.

Works alongside

  • Dialler or telephony platform
  • Email
  • SMS
  • WhatsApp or other messaging
  • CRM
  • Client delivery export
  • Call recording storage
  • Spreadsheet import
Common questions

Questions owners ask before a demo.

Does it place the calls itself?

No. Your dialler or phone system places them. This system keeps the campaign, list batch, outcome, callback and sale, and can take call results from the dialler through a connection set up with you.

How is a suppression list used?

Each entry holds the number, the source and the date. A new batch is matched against all entries before callers see it, and the removed count is shown to the manager.

Can two teams share one list without calling the same person twice?

Yes. Every record shows its attempts and its holder, and the gap rule blocks another attempt until the set interval has passed.

What happens when the client rejects a sale?

The sale returns to the caller’s team leader with the reason. The related incentive is reduced by the clawback rule from your plan, and the campaign report shows the rejection.

Can callers see their own incentive during the month?

Yes. Accepted sales update the running figure against the slab, and the caller sees the next threshold. Payroll still pays the amount.

Can it book meetings for the client’s field team?

Yes. An appointment holds time, address and contact, goes to the field representative, and is marked as visited or missed afterwards.

Does it check calls for required wording?

A listener scores sampled recordings against the script and consent lines you define. The wording itself is set with your advisers, not by the software.

How do old lists come across?

Past batches, outcomes and callback diaries are imported from dialler exports or sheets. Team leaders check a sample batch before the first live shift.

What does it cost?

No price is posted. Caller seats, clients and campaigns running side by side, and any dialler links all move the figure, and a quote reaches you once you have watched a demonstration.

Is it needed for a dozen callers on one product?

Maybe not just yet. A shared sheet and a dialler can cope until several campaigns, suppression lists and incentive slabs are running side by side at the same time. Share your requirements first.

Wondering what it would cost? Share your requirements and an engineer will come back with a scope.

Book a demo

See Outbound Sales Centre Management Software with your own data.

Tell us how you run things today. We’ll show you the parts that matter to you and say plainly what would need changing.

  • No obligation
  • A reply within one business day
  • Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements