Produced after your order is confirmed.

A separate Telegram account, produced with Premium already running

DragonSIM registers a new Telegram account for you and switches Premium on while that account is being built. Nothing exists in advance, so none of the term is spent waiting for a buyer. You set four parameters, support confirms feasibility, price and lead time, and only then does payment come into it.

Message support on Telegram

The brief you write below is the message. Support replies with feasibility, price and lead time before any payment.

3 days, the standard term.7 days for work that runs longer.

Write the request brief

Set the four parameters below. The message block updates as you go, and the control at the foot of the document copies the finished brief ready to paste into a message to support.

Terms of the request

  1. My own Telegram account is not involved in this request.
  2. No number, login or password of mine will be supplied.
  3. Renewal of Premium is not requested.
  4. No catalog position is being ordered here.
Premium term
  • The standard term. A brief that says nothing about duration is costed on 3 days.
  • The additional term, for work that runs longer than three days.
Delivery format
  • The folder the desktop client reads. Ask for this if you work in Telegram Desktop.
  • The authorisation file pair that compatible software reads.
  • TDATA and Session + JSON for every account in the brief. This is what the brief asks for unless you change it.
Write the country in your own words. Feasibility of the direction you name is confirmed before you pay.
Any number from one upward. Each account in the brief is produced with its own files and its own login data.

The message to send

Premium term:
3 days
Delivery format:
TDATA and Session + JSON
Country:
not stated yet
Accounts:
1

Support answers with feasibility, price and lead time. Payment happens only after you have approved those three.

Deliverables

  • One new Telegram account per unit, registered after the order is confirmed.
  • Premium already running on each account at handover.
  • Files in the format set above: TDATA, Session + JSON, or both.
  • Separate files and separate login data for every account in the brief.
  • The conversation in which the parameters were agreed stays open after handover.

  • GEOthe trade word for the country an account is registered on. You name it, there is no list to pick from.
  • Premium termthe number of days Premium runs on the account, 3 or 7, set inside this one request.
  • Lead timehow long production takes, quoted for your brief once the direction is checked.
Above this line, a request. You owe nothing and nothing has been agreed.

The line where a request becomes an order


Below this line, an order you have approved and paid for.

Why none of the term is spent before the account reaches you

If the account had existed before your order

  1. Registered before any orderThe account is created without a buyer in view, so the only place its Premium clock can start is there.
  2. The term runs while it waitsEvery day the account spends waiting for someone to buy it is a day taken out of the Premium term.
  3. You receive what is leftWhatever remains of the term at the moment of handover is all there is left to use.

Produced after your order is confirmed

  1. Nothing exists in advanceRegistration begins only once the four parameters are agreed and the order has been paid.
  2. Premium is activated during productionActivation is part of building the account, not a step performed after it reaches you.
  3. The term is running at handoverPremium is already active when the files and login data change hands, and none of the term went on waiting for a buyer.

The same term length. Two different places for it to start.

What the catalog settles, and what this brief settles

  • The catalog

    Country positions in the catalog are sold without Premium, and no position in it carries a Premium term.

    Browse the country catalog
  • This brief

    Premium is produced only through a request like the one above: on the country you name, in the quantity you set, with the term chosen inside the same request.

  • Delivery formats

    TDATA and Session + JSON mean exactly the same thing here as everywhere else in the store, and the choice is independent of the term.

    Compare the two delivery formats
  • Volume terms

    The terms that apply to large catalog orders are set out separately and do not describe this request, whose feasible volume is confirmed brief by brief.

    Read the wholesale terms

Questions that come up after the brief is written

  1. What is fixed when the request is confirmed, and what is only fixed at handover?

    Confirmation settles the four parameters together with feasibility, price and lead time, so the term length and the delivery format stop moving at that point. What does not yet exist is the account itself, its files and its login data. Those appear at handover, with Premium already running. Payment sits between the two moments: you approve the confirmed request, you pay, and production starts.

  2. The direction I named cannot be taken. What happens to the brief I have already written?

    You are told plainly that the direction is not available rather than left waiting, and a close alternative may be suggested. Everything else in the brief stands as written: the term, the delivery format and the quantity are unaffected, and only the country line changes. Nothing has been paid at that stage, because a brief is a request and not an order.

  3. What does the conversation cover once the files have been handed over?

    The conversation in which the parameters were agreed stays available after handover, so the agreed term, format, country and quantity and the handover itself stay on record where both sides can see them. It is not kept open for renewal: extending Premium is not part of this service.

  4. Do I pay before or after feasibility, price and lead time come back?

    After. The brief goes to support first, the three answers come back, you approve them, and only then is the agreed order paid. Production starts once payment is in, which is the reason the account does not exist beforehand.

  5. Should the brief ask for 3 days or 7 days?

    Ask for 3 days by default: it is the standard term, and a brief that says nothing about duration is costed on it. Ask for 7 days when the work you have planned runs longer than three days. They are two values of one parameter inside one request, not two products, and the choice has no bearing on the delivery format.

  6. What is left once the Premium term ends?

    The account carries on as an ordinary Telegram account and the Premium features stop. Renewal is not part of this service, so a further term is not something the brief arranges. The files and the login data handed over stay yours.