Pushing a campaign out to your tribes

Set Send From to Tribe Accounts and Gorilla Dash creates a separate child campaign for each tribe you select. Each one sends from that tribe's own SMS account, to that tribe's own people, at that tribe's local time.

Choosing the tribes

Pick All Tribes, By Tribe Type, or Select Tribes. Only tribes that are open or opening soon are included — a closed or pending tribe is skipped silently.

Local time, not your time

A SCHEDULED TIME IS RE-ANCHORED PER TRIBE

Schedule 10am and every tribe sends at 10am their time — so tribes in different timezones send hours apart. That is usually exactly what you want for a local offer, and exactly wrong for a simultaneous announcement. Know which you are doing.

Who pays

This is the only place the Who pays choice appears — Organisation pays puts the whole cost on head office, Tribe pays bills each tribe for its own. Tribes cannot change it afterwards.

Editing the parent rebuilds the children

ANY EDIT DISCARDS UNSENT TRIBE CAMPAIGNS AND RECREATES THEM

Saving a change to the parent deletes every child that has not gone out yet and builds them again from scratch. If a tribe had swapped in their own images, that work is lost without warning. Finish the parent before you tell tribes they can customise.

Locking images does not work yet

There is a Lock images for tribe child campaigns switch, but it is not enforced — tribes can still change the images regardless. Do not rely on it for brand control.

Watching it go out

The parent campaign shows a Tribe Results table — one row per tribe with its status, timezone, scheduled and sent times, and its own recipient, delivered and failed counts. A tribe stuck without a status usually has no SMS account connected.

Cancelling a push

If some tribes have already sent, deleting the parent asks you to confirm: the unsent tribe campaigns are cancelled and removed, the sent ones are kept, and the parent is marked as sent. Nothing already delivered can be recalled.