Skip to content
GullySales

BPO, KPO and contact centre companies · Website

Let a procurement team find the answers without booking a call.

A website for a BPO, KPO or contact centre company is where a buyer checks the process, the security approach and the proof. GullySales works on the structure, the documents and the service pages.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

A customer contact team working at desks with headsets

What website means

A website is the page a customer lands on after searching, clicking an advert or scanning a code, and it decides whether they call or leave. GullySales builds and maintains sites that load quickly, explain the offer plainly and make the enquiry form or phone number easy to find.

Last updated 14 Nov 2026.

For BPO, KPO and contact centre companies

Where it usually goes wrong, and what we would do.

  • “Buyers read before they call”

    An operations head or a procurement analyst scans the site for the process, the languages and the controls.

  • “Security and consent need a visible home”

    A page on data handling and recording, with a clear note on legal differences, speeds reviews.

  • “Service pages should be specific”

    Voice, chat, back office and research differ in questions and proof. One page cannot serve all.

  • “Proof is limited by contracts”

    Client names are restricted, so cases need unnamed accounts and a permission-based reference list.

What we do

What we deliver for BPO, KPO and contact centre companies.

The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.

  1. A structure by process and sector

    Service pages by process, with sector pages for lenders, insurers and retailers. The menu offers a buyer two ways in: by process, such as voice support or data entry, and by sector, such as healthcare or e-commerce.

    Result: A buyer finds the page for their work.

  2. A security and consent page

    How data and recordings are handled and where the client's adviser takes over. It states in plain words how data is handled, who has access, how teams are screened and how a consent is recorded, with a contact for deeper questions.

    Result: Security reviewers find answers.

  3. Process note downloads

    Readable notes for each service. Each download is a short PDF on one service, written for a buyer's operations head and linked from the matching service page.

    Result: Operations teams can see how the work runs.

  4. Case pages without names

    The process, set-up and lessons. A page describes the situation, the set-up and the change, with a sector label in place of a name and no figures the client has not approved.

    Result: Proof stands without breaching confidence.

  5. A pilot request form

    Fields for process, volume, language, systems and stage. The form asks for the process, the rough volume and the preferred start, and goes to a named person with a reply route set.

    Result: Each request arrives with the details needed.

  6. Performance and accessibility basics

    Pages that load on a corporate network and work on a phone.

    Result: Buyers can read the site anywhere.

  7. A page for each delivery location

    Buyers ask where the work is done, in which city, from which building and with what backup. Each page names the services run there and the continuity arrangements, and gives search a reason to show the right city.

    Result: A buyer finds the answer for their city.

How the result is measured

  • Page load time
  • Bounce rate
  • Enquiries from the website

Recorded as a baseline before work starts, so every later report has an honest comparison.

Searches your buyers type

What procurement teams look for on an outsourcing site.

BPO security and compliance practices
A security and consent page with access control, storage and recording practice. Review it with your legal adviser before launch.
process note download
A short pdf for each service. Gate it behind a simple form asking for name, company and process.
delivery centres and languages
A page listing locations and languages you really staff, kept current. A buyer will ask about any claim.
pilot request
A form that asks for process, volume range, languages and the date the buyer wants a conversation. No pricing on the page.
case study outsourcing without client name
An anonymised case page with the problem, the change and what the client owned. Written with client permission.

Who it is for

This is written for these BPO, KPO and contact centre companies.

  • Voice and non-voice BPO providers
  • Inbound and outbound contact centres
  • Back-office and data processing providers
  • Knowledge process outsourcing for research and analytics
  • Finance and accounting outsourcing
  • Collections and customer service outsourcing
  • Chat, email and social support providers
  • Healthcare and insurance claims processing
  • Multilingual and regional language support teams

Before you decide

When this may not be the right fit.

  • You have no one who can keep a delivery-centre page accurate, so a published list would soon contradict the floor.
  • Legal has not agreed what you may say about data handling, so a security page would be a risk.

Before you decide

Agree the work. Know how to judge it.

Website for BPO and contact centres: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

List the pages that support a buying decision and the actions visitors must complete. Keep examples of failed forms, unclear product information, and questions your team answers repeatedly.

Make the scope clear

Agree the page list, content ownership, integrations, and who controls the domain and hosting. Include redirects and existing search traffic in a redesign brief, before changing addresses.

Check the work in use

Complete a real enquiry journey on a phone and a laptop. Check that the confirmation appears, the enquiry reaches the right person, and tracking records the action once.

Know when to change course

If visitors can enquire but the team does not follow up, start with the sales handover. A larger website will not resolve that delay.

These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.

Before we start

What to have ready before the work starts.

The records, access and decisions this work needs from BPO, KPO and contact centre companies. Anything missing is noted in the written scope, with who will supply it.

The domain and hosting in the company's name
The account that holds the web address and hosting, in the company's own name. Some sites sit under a former agency's login. Until the company holds both, we cannot launch, and moving them becomes the first task. Include the hosting login and a note of any plan that renews each year, so the site does not lapse unexpectedly.
Process descriptions from delivery leads
A written description of each process you run, covering what is handled, the languages, the tools and how quality is checked, from the person who runs it. The service pages are built on these. Where a description is thin, the page is held back. Mention also the tools used, such as ticketing, quality scoring and dialler, only at the level you are happy to state in public.
The security papers you may publish
Policies and certifications your compliance lead agrees can be described in public. The security page uses only these. If nothing can be shown, the page explains the approach in general terms and offers documents under agreement. Date each paper, and give us the name of the person who approved it, so we cite the current version and not an older one.
A decision on which locations to show
Whether the site lists delivery centres, remote teams or neither, and how precisely. Some clients prefer locations private. Without a decision, the site names the cities served and leaves addresses off. Include also the legal names of the group companies, since a buyer's reviewer checks the site against the contract.
A pilot request form your sales team will read
The questions a buyer should answer when asking for a pilot: process, volume, language and timing of need. The sales head decides them. Without a form, requests arrive as loose emails and the team spends time asking for basics. Include also the contact the form notifies and who covers when that person is away, so no request is left unread.

How it works

How the website work runs

The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.

  1. 1

    Read the site as a procurement reviewer would

    We open the site the way a buyer's reviewer would, looking for the process, the security approach, the locations and the proof. You tell us which questions you are asked in every bid, so we know what the site must answer before the first call. We also note where a reviewer would look for the data protection lead and the continuity plan.

  2. 2

    Collect the policies and delivery details

    We collect the security and data summaries, the list of languages and locations, and the descriptions of each process from the delivery head. Your compliance lead marks what may be published. Anything confidential stays off the site. We also ask the delivery head to confirm that every language and location listed is true today, not planned.

  3. 3

    Draw the structure by process and sector

    We draw a sitemap with a page for each process, pages for the sectors you serve, a security page and a pilot request page. You approve the structure before any page is written, and you say which pages must wait until the floor can support them. We also write short bridges between the pages, so a buyer reading the claims process page can reach the security page in one step.

  4. 4

    Write the security and consent page with compliance

    We write the page with your compliance lead, in plain language, covering how data is handled and how consent is recorded. Your adviser reads it line by line. Details that need a signed agreement are marked as shared on request. Your adviser reads the whole page for rule references, and we leave out any numbered rule so that the page does not go stale.

  5. 5

    Review the test site with sales and delivery

    We put the pages on a private address and walk through them with the sales head and the delivery head. They check facts, names and the pilot request form, and we correct what they find before launch. We also test the pilot request form and the download links on a phone, and the sales head confirms the notification reaches the right inbox.

  6. 6

    Read requests against the earlier record

    After launch we compare pilot requests from the site with the record of enquiries, requests and pilots kept before the work began. You decide what to change, and who keeps the pages current when the services change. We also give you a list of the pages and the person who owns each, so a new language or a closed location is entered by the right hand.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design, at stage 1, prospecting and lead generation. The audit comes before it, and sales management keeps it running.

  1. Step 1

    Sales audit

    Find where deals are being lost and what to fix first.

    Start here if you cannot say where orders are lost.

  2. Step 2 · you are here

    Sales process design

    One written way to sell, from first enquiry to repeat order.

    Start here if every salesperson sells differently.

  3. Step 3

    Sales management

    A target, a review routine and someone who owns the number.

    Start here if the team has targets and no routine.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

Do we need a client logo wall?
Only with written permission. Without it, use unnamed cases. Only with written permission from each client, and the contract may forbid it. Without logos, show sectors served, the processes handled and the length of relationships you are allowed to state.
Should the site list our centres?
Yes where they exist and the buyer needs location and language information. Do not list places where you have no operation.
Do we need a careers section on the same site?
Yes, but keep it separate from the buyer paths. Candidates and buyers want different information. Keep it on the same site but separate it in the menu. Job seekers and buyers want different pages, and a clear split stops hiring content from crowding the service pages.
Do we need a client logo wall?
Only for clients who have agreed in writing. Some outsourcing contracts forbid naming the client, and a logo shown without leave can end the account. A page that explains the process and the controls convinces a reviewer better than borrowed names.
Should the site publish price or pricing models?
Publish how you price, such as per seat, per transaction or per outcome, without giving a rate. Buyers want the shape of the deal before they call. Rates depend on scope, so they stay off the page. Your sales head decides how much of the model to explain, and we write it plainly with an invitation to request a quote. Where a buyer's procurement team needs a formal rate card, it is sent after a scoping call, never published. The page also says which parts of the price move with volume, language or hours of coverage, so a buyer understands the shape before asking.
Do we need separate pages for each client sector?
Only for sectors where you have real experience and something particular to say, such as the way claims differ from collections. A sector page should name the processes, the compliance concerns of that field and the kind of pilot you would suggest. Thin pages with a sector name swapped in do harm. We start with the two or three sectors that bring the bulk of your work and add more when you have the material. A buyer who finds a general page may leave. A sector page that names the process, the compliance concerns and the pilot you would suggest is more useful. We write each from what your delivery head and account managers tell us, not from a template.
How long is the contract?
The term is agreed in writing after we have spoken, along with the fee and the reporting. It is never a default twelve months, and renewal is decided on the numbers against the baseline recorded at the start.
How soon will we see results?
It depends on the trade, the channel and what is already in place. After we have read your brief and spoken to you, we say what we would expect to move first and how it will be measured against the baseline. Nothing here is guaranteed.
Who will actually do the work?
The person you speak to before anything starts. We work from one office in Nagarbhavi, Bengaluru, with no account managers in between.
What do you need from us?
Your brief, and a conversation. After that, access to whatever this work touches, such as your website, your accounts or your enquiry record, and time with the people who handle your enquiries.

Your next practical step

Tell us what you are trying to grow, and we will read it before we call.

Eight short steps, mostly taps. Skip anything you would rather answer on the call.