Sender replacement rules at the aggregator level work differently from client-level rules. While client rules apply to a specific client's outgoing traffic, aggregator rules apply to all traffic sent through that aggregator, regardless of which client sent it. This is useful for destinations where certain sender names are blocked or restricted by the operator.
Go to Current Traffic → Routing → Aggregators.
Click the view icon next to the aggregator you need.
Open the Replacement rules tab.
Click Create in the Sender replacement rules block.
In the window that opens:
Fill in the fields:
|
Field |
Description |
|
Destination |
The country or network this rule applies to |
|
Client (optional) |
Apply this rule only to traffic from a specific client. Leave empty to apply to all clients |
|
Priority |
Order in which rules are checked – lower number means higher priority |
|
Sender |
The sender name to look for in outgoing messages |
|
Senders |
The name to replace it with. You can enter multiple names – one per line – and the platform will pick one at random for each message |
|
Ignore Case (optional) |
Match the sender name regardless of capitalisation |
Click Save.
The rule will apply to all matching traffic sent through this aggregator from that point on. This is particularly useful for destinations where certain sender name formats are required by the operator or where specific names are blocked.
