Terms of Service

1. These terms, and who they apply to

These terms cover your use of Rangeholder, web software that tells you, line by line, which of your existing numbers will move to a new contact center provider and which won’t, and that sends and follows up written requests about the ones nobody has answered, once your porting lead approves them. They are a contract between Rangeholder AB, of Första Långgatan 30, 413 27 Göteborg, Sweden (“Rangeholder”, “we”) and the company that signs up (“Customer”, “you”).

The service is for businesses only, not consumers. By signing up you confirm that you are acting for your business and that you have the authority to commit your company.

The person who accepts these terms accepts them for the company, not for themselves. If you don’t have that authority, please don’t go ahead.

If documents disagree. This order applies: (1) a signed order form or agreement between us, (2) the data processing agreement, (3) these terms, (4) our Privacy Policy, (5) anything else on our website.

2. What the service is

The list itself. Loading and combining your three sources. A usage profile for each number from 90 days of call records. A check of every row against published numbering data. The review queue. One of four statuses on every row, with the rule or the carrier’s exact words behind it. Written requests to the providers you name, drafted under the letter of authority you sign, sent once your porting lead approves them, followed up weekly and answered on their rows. User roles for your team, including the porting lead who approves requests. Versions, a locked cutover baseline, dated PDF and CSV exports, and as many read-only links as you like. All of it is inside the per-site fee, and nothing on that list is a separate line on any quote.

3. What the service is not

These limits are deliberate, and they are part of what you are buying. They are not defects.

Not a phone provider. We hold no numbers, carry no calls and never move a number ourselves. We can’t be the provider your numbers move to, and we will never appear on a porting form as one. Worktual sells the numbers and the connection under one telecoms agreement. A buyer who wants a single supplier for the whole chain should buy from a provider, not from us.

Not a contact center platform. No queues, no IVR, no agent desktop, no recording, no ticketing, no chatbot, no voice bot, no CRM, and no reporting on anything a customer experienced. We hold rows about numbers. Nothing here carries or answers a call.

Not a forecast. We publish no odds that a number will move and no predicted date for a carrier’s answer. A status comes from published numbering data, with the rule named, or from a carrier’s own written words, or it says no answer yet. Nothing in this service estimates, scores or predicts an outcome. If you want a number to be movable, there is no way to make the list say so.

Not legal or regulatory advice. Our list says what published numbering data shows and what a provider wrote. It is not advice on your contract, your minimum term, your notice period, your regulatory duties or your rights against a provider, and no status in it is an opinion on any of those. Take those questions to your own lawyer.

4. What you need to do, and why it matters

What you get from the service depends a lot on things only you control. Please read this section carefully, because sections 9 and 10 build on it.

Finding the three files. Your numbers spreadsheet, your current provider’s latest bill, and 90 days of inbound call records have to come from you. At most companies they sit with three different people, and this is the slowest part of week one. We can’t check a number nobody told us about. A number missing from all three files won’t appear in the list.

Working through the review queue. A suggested status is applied only after one of your users confirms it, row by row. A list can’t be locked as a cutover baseline while unclear rows remain, and nobody can override that. Someone on your side has to own the queue. This is the job most likely to slip in week two.

Signing the letter and approving requests. No request can go to the provider you are leaving until you sign it, so the days it sits with legal are days nothing is asked. You are also responsible for making sure the person who signs has the authority to do so on the account. You name a porting lead for each site, a user on your side who approves every request before the software sends it. A request waiting for that approval is not sent.

Naming the providers. You enter who you are leaving, and who you are joining once you have chosen. Requests go only to the providers you name. We don’t choose, recommend or approach a provider for you, and some questions about coverage can’t be answered until you have named the carrier you are joining.

Reading the list before you announce a date. The cutover date and the note to your customers are yours. We give you a locked, dated version showing which rows are answered and which aren’t. Whether that is enough to announce a date is a call only you can make, and we won’t make it for you.

Your legal basis for the call records. You are the controller of the call records you load. Before the first file is sent, you need to be satisfied, along with your data protection officer, that sharing them with a processor for per-number usage profiles is within your legal basis. We will give them whatever they need to assess it.

5. Getting started, and what is free

The first site’s list is built and delivered before any payment. Upload the three files, get the combined list and the dated statement, and pay only if you keep it.

No card is needed to start, and the price per site is public without speaking to anyone.

The build includes the full setup: loading, combining, usage profiles and the first complete check against numbering data across all your numbers.

If published numbering data answers everything cleanly and no request needs to go to a provider, the statement says so and we will tell you not to buy. That really happens with a small single site.

6. Fees

One published price, per site, per year. $7,400 per site per year, invoiced yearly in advance. With 2 to 5 sites it is $6,300 each, and with 6 or more it is $5,200 each. The figure on the site is the figure on the order form. There is no quote step and no call before it.

Nothing else is metered. Numbers on the list, however many. Users and read-only viewers, however many, including your project manager, your procurement lead, your current provider and the platform you are evaluating. Versions, locked baselines and exports. Requests and follow-ups sent to providers, however many rounds a carrier takes. None of these is a line on any quote we issue.

Setup is not charged. Loading, combining, usage profiles and the first full check are part of the subscription. We don’t sell implementation days, we have no professional services line, and no partner sells one for this product.

The service credit is automatic. If an open row goes ten working days with no update, one twelfth of that site’s annual fee is credited on the next invoice, without you having to claim it. Days a request waits for your porting lead’s approval don’t count. The promises behind the credit are ours alone: a first status on every number within two working days of the last file, the written request drafted and ready for approval within two working days of the signed letter, and every carrier reply posted to its row within one working day of arriving.

Term, renewal and leaving. Twelve months, then month to month. To cancel, write to a named person at Rangeholder, not a form inside an account page. It takes effect at the end of the month you send it. There is no minimum term beyond the first year, no automatic renewal for another fixed period, and no early-termination or recovery charge of any kind. The price is held for 24 months from signing. After that it can change once a year with 90 days’ written notice, and any change gives you the right to leave at the old price.

7. Delivery, availability and support

The list and how it updates. The combined list is delivered within two working days of the last file arriving, with a first status on every row. After that it updates whenever a file is reloaded, a user clears a review item or a carrier reply is posted. It also updates every time the numbering data is republished, which triggers a fresh check of every row.

Requests to providers, approved on your side. The software drafts the written porting request to each provider you name, from your list and the letter you signed. Your porting lead, a named user on your side, approves each one in the product before it is sent. After that the software follows up weekly, posts every reply word for word on the row it belongs to, and alerts your porting lead if a request goes 15 working days unanswered, with an escalation drafted for them to approve. No request agrees, orders or changes anything on your behalf, and nobody at Rangeholder writes to a provider for you.

What we commit to, and what we don’t. We commit to three countable things, all of them ours: two working days from the last file to a first status on every row, two working days from the signed letter of authority to the written request drafted and ready for your porting lead’s approval, and one working day from a carrier’s reply arriving to it appearing on its row. We make no promise about when a provider or carrier answers, because we have no way to hold them to one. We would sooner say that than publish a target we can’t keep.

Availability, stated plainly. We publish a status page with incident history. The list is a document you can hold as an export, so an outage of the web app doesn’t put your cutover at risk the way an outage of a phone line would. We offer no availability credit, because it would be theater. The credit we do offer is tied to the commitments above, which are what would actually cost you a date.

Support. Support is by email at [email protected]. We aim to reply within one business day. That is a target, not a guarantee.

8. The list, its versions and the locked baseline

A locked version can’t be changed. Rows, statuses, rules, carrier answers, source references and review history don’t change after a version is locked as the cutover baseline. A date was announced against it, and it has to stay readable as it stood that day.

Corrections are new versions. A correction creates a new version with the reason, the author and the date. The older version stays readable and is marked as replaced, not removed. So the difference between what was known the day the date went out and what is known now stays visible.

Carrier answers are kept word for word. Where a status came from a provider and not from published data, the provider’s own written words are stored next to the row, with the sender and the date. We don’t summarize a carrier’s answer into a status and then throw the answer away.

Export, and life after the subscription. The list, every version, the statuses and their sources, and the correspondence export as CSV and dated PDF at any time, without asking us. The row format is published, so the archive stays readable after you stop paying for the software.

9. What we promise, and what we don’t

We promise to provide the service with reasonable skill and care, and that we have the right to provide it.

We promise that a row’s status is what the published numbering data or the stored carrier answer behind it actually supports. The files we received are kept unaltered. No model can write to the status column. A list can’t be locked with unclear rows in it, and a locked version isn’t changed afterward. We don’t promise that a number will move, that a provider or carrier will answer, that it will answer within any period, or that an answer we are given is correct. We don’t promise that published numbering data is current or accurate. We name it and date it, and it is published by bodies we don’t control. We don’t promise that a file you supply is complete, and a number missing from all three files is missing from the list.

Beyond that we give no other warranty. As far as the law allows, we exclude all implied warranties, including merchantability, fitness for a particular purpose and non-infringement.

10. Liability

10.1 Neither of us limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for anything else the law says can’t be limited.

10.2 Losses neither of us covers. Neither of us is liable for lost profit, revenue, expected savings, business, goodwill or reputation, or for any indirect or consequential loss, however it arises.

10.3 Specific exclusions. We can’t be liable for work we deliberately stay out of. We don’t move numbers, so we are not liable for a port that fails, is delayed, is rejected or goes to the wrong provider. We are not a phone provider, so we are not liable for any interruption, misrouting, caller ID problem or loss of service on any number, before, during or after a cutover. We don’t forecast, so we are not liable for a cutover date you set while rows still said no answer yet. The list shows which rows are open, and locking a version with open rows in it is a decision the product records and does not make. We don’t advise, so we are not liable for a contract or regulatory position taken on the strength of anything in the list. And a number that was never supplied to us is outside everything above.

10.4 Cap. Our total liability is capped at the fees paid for the affected site in the twelve months before the claim. If a status misstates the data or the carrier answer behind it, the practical remedy is a corrected version within two working days at no charge, with the reason and the author, the older version left readable, and the automatic service credit where one applies.

10.5 You accept that the limits in sections 9 and 10 are a fair way to share risk, given the price and your part under section 4, and that we could not offer the service at this price without them.

11. Confidentiality and data

Your numbers are your confidential information, and we treat them that way. Inside Rangeholder, nobody opens them unless your admin grants support access for a named ticket. A full list of numbers with each one’s call pattern describes your sites, your queues, your busy seasons and which of your lines are dying. We won’t share it with any provider other than those you name in the letter of authority, we won’t share it with another customer, and we publish no figure drawn from it. Your call records are your callers’ personal data before they are anyone’s confidential information, and are handled under Part B. Our own confidential information is the label classifier, the shared label set, our library of bill formats and how we implement the numbering rules.

How we handle personal data is set out in our Privacy Policy and in the data processing agreement between us, which forms part of these terms. If the DPA and these terms disagree about personal data, the DPA wins.

12. Who owns what

Your numbers, call records, list, statuses, correspondence and locked versions are yours. We license you nothing over your own data and claim nothing in it.

What we license to you is the software, the numbering rules, the row format and the export format.

The row format and the export format are published under an open license and sit outside the paid subscription, so a statement exported from Rangeholder stays readable by whatever you build or buy next.

You may show anything the list produces to your board, your auditor, your lawyer, your current provider, a competing vendor or a regulator. Nothing here stops you publishing benchmarks, performance or quality information about Rangeholder, and nothing ever will.

We claim no right over any carrier’s written answer stored in your list. It was written to you, under an authority you gave, and it leaves with you.

You may not use our name or logo in public, and we may not use yours, without written permission first.

13. How long this lasts, and how it ends

13.1 The contract starts when you sign up and runs until one of us ends it.

13.2 You can end it. Cancel at any time. It takes effect at the end of the current billing month, unless section 6 sets a minimum term.

13.3 We can end it. We can end it with 30 days’ notice. We can end it immediately if you seriously break these terms and don’t fix it within 14 days of being told, if you become insolvent, or if your use exposes us to legal risk.

13.4 What happens then. We stop delivering and stop billing. You keep everything already delivered to you, and your right to use it continues. We delete or return our working copies as the DPA says. Sections 9, 10, 11 and 12 continue to apply.

14. Changes to these terms

We may update these terms. A change that matters takes effect 30 days after we email you about it. If you don’t accept it, you can end the contract before then. Using the service after that date means you accept the change.

15. Contact

Rangeholder AB, Första Långgatan 30, 413 27 Göteborg, Sweden
[email protected]

← Back