PE-TM Chain Status Explained: Pending, Approved, Rejected & What To Do
You created the PE-TM chain, and now the portal shows a status you are not sure about: Pending, Pending with PE, Pending final approval, Registered, Active, Rejected, Blacklisted. Each operator DLT uses slightly different words for the same lifecycle, and with the TRAI PE-TM Binding Framework enforcing blocking from 30th September, the difference between “Pending” and “Active” is the difference between delivered and dropped. This guide maps every status you will see on Jio, Airtel, Vi, BSNL, Tata and Smartping to what it means and what to do next.
Signup NowSchedule Free Meeting
The chain lifecycle in one picture
Whatever the portal calls it, a PE-TM chain moves through the same stages:
- Requested / Pending with TM: you (the PE) created the chain naming a TM-D; the telemarketer must accept it.
- Pending with PE / Pending final approval: the TM-D accepted; on several portals the PE must now confirm once more.
- Registered / Active / Approved: both sides approved; the chain is live and its hash is what operators validate against.
- Rejected / Blacklisted / Inactive: declined, expired or suspended; no valid chain exists for that route.
Only stage 3 protects your traffic. Everything else counts as “no approved chain” once blocking mode is on.
Status names by operator portal
| Portal | Waiting on TM | Waiting on you (PE) | Live | Failed |
|---|---|---|---|---|
| Jio TrueConnect | Requested | Pending for Approval (Approve / Reject action) | Registered, Chain Status Active | Rejected |
| Airtel | Pending | Pending with PE (View Workflow → Approve) | Active, “PE TM Chain is Completed” | Rejected |
| Vi (Vilpower) | Approval Status Pending | Chain State Pending (Approve on the lineage view) | Chain approved, Status Active | Rejected / Suspended |
| BSNL | Approval Status Pending | Pending (final approve after TM accepts) | Approved, Status Active | Rejected |
| Smartping / Videocon | Pending PE-TM Chain | Pending final approval (Chain Flow → Approve) | Registered PE-TM Chain | Rejected / Blacklisted |
| Tata | Submitted | PE approval where prompted | Listed in PE TM Binding List as active | Rejected |
Click-by-click screens for each portal: Jio, Airtel, Vi, BSNL, Tata, Smartping.
The step most people miss: the second approval
On Jio, Airtel, Vi, BSNL and Smartping, the chain is not live when the telemarketer accepts it. The request comes back to the PE for a final confirmation: “Pending for Approval” on Jio, “Pending with PE” on Airtel, “Pending final approval” on Smartping, the Approve button on the lineage view on Vi. Chains sit in this state for weeks because nobody logs back in. Until you press Approve, there is no active chain and no valid hash, and the mismatch warnings keep coming.
Rule of thumb: after your TM confirms they have accepted, log in to each portal the same day and complete the PE-side approval.
What each status means for your traffic under the framework
| Status | Before 30th September | After 30th September |
|---|---|---|
| Active / Registered | Delivers, no warnings | Delivers |
| Pending (any kind) | Delivers with mismatch warnings | Blocked |
| Rejected / Inactive | Delivers with warnings | Blocked |
| No chain created | Delivers with warnings | Blocked |
Rejected? Here is why, usually
- Wrong TM-D selected: you picked a telemarketer that does not carry your traffic, or a TM-A instead of the TM-D. Create a fresh chain with the correct TMD ID.
- TM never accepted: the provider ignored the request; aggregator panels often have no one watching the DLT inbox. A responsive TM-D accepts within hours.
- Entity mismatch: chain raised from a PE ID that is not the one your traffic uses.
Fast2SMS accepts chain requests to its TMD promptly on every portal, and support walks you through the PE-side approval:
Bind to Fast2SMS: SID GROUPS PRIVATE LIMITED · TMD ID 1702178720558766591
Registered TM-D with direct connectivity to Airtel, Jio, Smartping, BSNL and Tata. Automated DLT with auto approvals, free DLT support, no setup or monthly fee.
Chain stuck in Pending or Rejected? Our team will sort it with you, free.
Share your screen for ten minutes and we complete the binding on every operator together. Schedule a free meeting, call +91-6262778811 or email [email protected].
Watch: the PE-TM mismatch warning explained on screen
Frequently asked questions
My PE-TM chain says Pending. Is my traffic safe?
No. Only Active/Registered chains protect traffic under the framework. Pending chains are treated as unapproved and will be blocked after 30th September.
The TM accepted my chain but it is still Pending. Why?
Most portals require a second, PE-side approval after the TM accepts (Pending for Approval, Pending with PE, Pending final approval). Log in and press Approve.
How long does chain approval take?
Creating the request takes minutes. A responsive TM-D accepts within hours; your final approval is immediate. Whole flow: same day when both sides act.
Do I need one chain per operator?
Yes. Bindings are per DLT platform. Bind the same TMD ID on Jio, Airtel, Vi, BSNL, Tata and Smartping.
Can I have chains to two telemarketers?
Yes, a PE can bind multiple TMs. Each route your traffic actually uses needs its own approved chain.
What does “Chain Flow” or “Lineage” show?
The path PE → TM(s) → TM-D with each hop’s status. It is where the final Approve button usually lives.
What is Fast2SMS’s TMD ID for binding?
SID GROUPS PRIVATE LIMITED, TMD ID 1702178720558766591.
Who can help me finish a stuck chain?
Free meeting at fast2sms.com/meet, sales +91-6262778811 / [email protected], existing accounts [email protected].
Get every chain to Active before the deadline
Check each portal, finish every second approval, and bind to a TM-D that actually accepts. Signup free and we will help you do it today.
Signup NowSchedule Free Meeting
Sales: +91-6262778811 · [email protected] | Support: [email protected]