Por enquanto, este guia está só em inglês.
BikeKit talks to riders in three ways: service messages about the service (a station closed for works, a festival), notifications it sends by itself (a ride's receipt, a pass about to end), and email campaigns to riders who agreed to marketing. Everything is written in Portuguese and, optionally, English; each rider reads their own language, and gets the Portuguese where no English was written.
Service messages
Messages → Service messages is where the control room writes to riders about the service, and sees what was sent, its state (Scheduled, Showing, Ended, Withdrawn) and how many riders read it.
To send one:
- New message.
- To: Every rider, or Riders of some stations and choose the stations. A station's riders are those who started or ended a ride there in the last 30 days.
- Kind: Information, or Disruption for something that stops riders using a station. A disruption also shows on the station itself in the app. Messages to everyone or to stations appear in the open data feed as well.
- Write the title and message in Portuguese, and in English under Also in English if you like.
- Shows: Now or From a date, and Until a time, or empty to show it until withdrawn.
- Send (or Schedule). Riders it reaches get a push notification and find it in the app.
Withdraw takes a message down at once, or cancels one that hasn't started, with a reason.
Closing a station, a zone or the whole system can send a disruption message too (see Closures); lifting the closure withdraws it. Support writes to one rider from the rider's page.
Notifications
BikeKit sends these by itself, by push to the rider's phone, by email, or both:
| Notification | When |
|---|---|
| Ride started | A ride starts |
| Ride receipt | A ride ends, with its time, distance and charge |
| Low balance | The wallet goes below €2 |
| Pass ending | A pass ends within three days, unless a longer one follows |
| Fault report received, Fault report answered | A rider's fault report is received, and its work order is done or cancelled |
| Service message | A service message reaches them, including a closure's and Support's answer to a call for help |
| Ride running long, Bike not returned, Paused too long | See alerts |
| Document verified or rejected | Support decides on a document |
| Direct debit notice | Support collects by direct debit |
| Badge earned; referral rewards | See Badges and Referrals |
| Password reset, data copy ready, privacy request refused, account closed | Sent at once by the server |
| Campaign | An email campaign |
Riders choose, in the app, which kinds they take by push and by email: rides, wallet and passes, and service. Account messages always go by email. Marketing goes by email only, and only to riders who agreed to it.
Messages → Outbox lists every notification sent, by state (Waiting, Sent, Retrying, Failed, Cancelled), channel and kind, with counts. Resend sends one again to the rider's address now. A provider that's down is tried again four times over half an hour. A message the mail server refuses for good, such as an address that doesn't exist, is Failed with the server's reason, and isn't tried again.
Messages → Templates holds the words of each notification. Managers change a template's words in both languages, turn its push or email on or off, or turn it off altogether; account messages can't be turned off. In the words, {field} puts in a value such as the ride's charge. Every email adds the scheme's name, a link to the app and a line saying why the rider gets it, so the words need none of these.
Campaigns
Messages → Campaigns is Marketing's. A campaign is an email to a group of riders, sent only to those who agreed to marketing.
- New campaign: a name for staff, the subject and message in Portuguese, and optionally English.
- Choose who: Every rider, those who Rode lately (in the last so many days), those who Stopped riding, or those who Holds a pass of a kind.
- Save draft. The draft shows how many riders are in the group and how many of them agreed to marketing.
- Send campaign, after a confirmation. It goes once; cancelling it stops the emails still waiting.
Each campaign email ends with a link to stop getting news, as the law requires. A rider who follows it no longer agrees to marketing, and gets no further campaigns.
Badges
Badges reward riders for goals they reach, with points.
Settings → Badges lists the catalogue: each badge's goal, its points, how many riders hold it, and whether it is still being given out. BikeKit comes with thirteen: the first ride, 10, 100 and 500 rides, 100 and 1,000 km, 10 and 100 kg of CO₂ avoided, 10 balancing bonuses, 25 and 100 stations, and 7 and 30 days in a row.
New badge (Marketing):
- A name and a description riders see, in Portuguese and optionally English.
- The goal: Completed rides, Distance ridden, CO₂ avoided, Rebalancing bonuses, Different stations or Days in a row, and how many.
- The points it gives, then Create badge.
A new badge is given at once to every rider who already meets it (Giving out shows while that runs). A badge's goal and points never change once made, so a badge keeps its meaning; Manage changes its words, or Retire stops giving it out while those who have it keep it.
Referrals
Every rider has a referral code to share. When a new rider signs up with it and completes their first ride, both get wallet credit.
Settings → Referrals shows the terms, this month's sign-ups with a code, rewards and money paid, and every referral by state: Waiting for a ride, Rewarded or Void. Change terms sets:
- Each of the two gets: the credit (€1 by default);
- Code accepted for: how many days after signing up a rider may still give a code (30);
- Paid referrals a month: the most a referrer is paid for in a month (10).
A referral past the month's cap, or to a suspended or closed account, isn't paid, and says why. Referral credit is a gift: not invoiced and not refundable to a bank.