Ride-Hailing App Development

Ride-Hailing Passenger and Driver Tags: Dynamic Rules vs Manual Labels

A promo, a courtesy policy, or a watch list is easy to describe and hard to apply when every passenger and every driver sits in one undifferentiated roster. If customer service has to remember who is who, the rule dies on the second shift. Ptaxi’s ride-hailing app documents audience tags for passengers and drivers: staff can view and manage tagging rules, view the people who currently have a tag, and choose dynamic or static tags.

This is an admin tagging surface. The list does not describe a passenger-facing “your tags” page, and it does not say a driver sees these labels in the app. Keep the walkthrough on the admin rules and the tagged lists.

What audience tags actually are

Under Audience Tags, Passenger Tags let staff view and manage passenger tagging rules and view tagged passengers. Tags are dynamic or static. Dynamic tags are applied automatically when configured conditions are met. Static tags are applied manually by customer service in the backend.

Driver Tags use the same structure: rules, a list of tagged drivers, dynamic versus static, and manual static tags from customer service.

Hold those two screens together. The useful work is a rule plus a current membership list, not a slogan on a campaign brief. One policy applied to the whole fleet is simple to announce and sloppy in practice. A named tag, with a list of who currently has it, gives staff a place to look before they write the next exception by hand.

Do not confuse this with Rating Tags. That is a different screen: configuration of rating tags, cancellation reasons, complaint reasons, and refund reasons. If a buyer asks about “tags” in a demo, open both and say which one you are training. Rating tags are reason labels on a rating or a ticket. Audience tags are people labels.

Dynamic rules versus manual labels

Dynamic tags exist so a condition can label people without a ticket queue. The list confirms that conditions can be configured. It does not name the fields. Do not invent spend, cancel rate, city, vehicle type, or tenure as product facts. Operators will want to decide those conditions in a demo. Write down the fields the build actually offers. Until then, brief it as “configured conditions,” not as a published rule catalog.

That missing field list is a real tradeoff, not a footnote. A dynamic tag stays current if the conditions are right. Bad conditions create noisy tags, and a noisy tag is worse than no tag, because staff start to trust the label. If you cannot yet say which attributes the rule can see, do not pretend you already know how clean the membership will be.

Static tags exist for the cases a rule cannot see, or should not decide alone. Customer service manually tags passengers or drivers in the backend. That is useful for a courtesy flag, a watch list, or a one-off exception. It is also a maintenance job. A static tag that nobody reviews becomes stale, the same way a bad dynamic condition tags half the fleet.

The list lets you view tagged passengers and tagged drivers. Train that list as the check: after a rule fires, or after a manual tag, open the membership and confirm who is on it. The list does not document an automatic untag, an expiry date, or a history of who applied a static tag. Confirm those behaviors in a demo. Do not sell them as facts.

When you train the two modes side by side, use one concrete pair, not a philosophy slide. Pick a dynamic rule you are willing to live with if it fires overnight, and pick a static label you are willing to review next week. Then open both membership lists. The pain this feature is meant to solve is the one-policy-for-everyone habit. The capability is a rule-based auto tag plus a manual static tag, with a list of who currently has it. The tradeoff sits in the same sentence: dynamic tags stay current only if the conditions are right, and static tags stay precise only if customer service maintains them.

What tags do not do on this product

Do not invent tag-based automatic dispatch. Do not invent tag-based pricing. Do not invent a passenger-facing page where a rider inspects or edits “your tags.” Those would be neighboring products, and they are not in this list.

A natural question is whether tags feed marketing. Reward campaigns are a separate admin tool, joined by passengers and drivers in the app. Tags can help staff find an audience they want to think about. The list does not say audience tags automatically attach to reward campaigns. Do not brief a spending campaign as “applied to this tag” unless a demo shows a documented link, and even then, do not upgrade a demo click into a feature-list claim.

The same caution applies to coupons, pushes, and geofences. Those tools exist elsewhere in the ride-hailing admin. This article does not claim a tag is the targeting key for any of them. If your operations team wants a tag to drive a campaign, say that as a process they will confirm in a walkthrough, not as a product switch already written down.

Keep the training on the admin surface

Because this is an admin tagging surface, do not add passenger-app or driver-app steps to the script unless you have also found a documented in-app tag view. The list does not give you that view. Staff build or edit the rules, customer service applies static tags, and anyone with access can open the tagged lists.

That limit is easy to oversell. A tag that only lives in admin can still be useful for support and operations. It cannot be briefed as a badge the passenger sees, or as a label the driver is coached to “earn.” If a buyer wants a public badge, write that as a gap, not as a hidden screen.

It also helps to agree on language before the demo. Call these audience tags, or passenger tags and driver tags. Do not call them rating tags, and do not call them “the targeting engine.” Staff should be able to answer three questions after the walkthrough: where the rule is edited, who is allowed to apply a static tag, and where the current membership is listed. If those three answers are clear, the feature is usable. If any of them is fuzzy, the tag will be treated as decoration.

What not to promise on audience tags

Do not promise that a tag changes who receives a job, or what a trip costs. Do not promise a rider or driver can see these labels in the app. Do not publish invented condition fields as if they were in the list. Do not say static tags expire, or that dynamic tags re-evaluate on a named schedule, unless the build shows it and you label that as a demo observation. Do not fold Rating Tags into this walkthrough. Do not claim tags auto-attach to reward campaigns.

A short ops checklist before you brief the admin

Keep this to one page.

  • Open Passenger Tags and Driver Tags. Say out loud that both have rules, a tagged list, and a dynamic versus static choice.
  • Create one dynamic passenger tag. Set a condition from the fields the build actually offers. Do not name spend or cancel rate unless that field is on the screen.
  • Trigger or wait for the condition on a test passenger, then open the tagged-passenger list and confirm membership.
  • Create one static driver tag and have customer service apply it in the backend. Open the tagged-driver list and confirm the same check.
  • Open Rating Tags on a different screen and point to rating tags, cancellation reasons, complaint reasons, and refund reasons, then close it. Keep reason labels off this card.
  • If someone asks about campaigns, open reward campaigns only long enough to say tags can help staff find an audience, and that the list does not attach tags to those campaigns automatically.
  • Write down anything the build shows about untag, expiry, or a history of who applied a static tag, and label those notes as demo observations.

If a script starts promising dispatch, pricing, or a passenger-facing tag page, cut it back to rules, membership lists, and the dynamic versus static split.

Close

Audience tags are a way to stop applying one policy to the whole fleet by memory. Staff manage passenger and driver tagging rules, choose dynamic or static, and view who currently has the tag. Dynamic tags follow configured conditions. Static tags are applied by customer service. The membership list is the check that the label is still true.

That is enough to brief a tagging practice. It is not enough to sell automatic dispatch, tag-based pricing, named condition fields, or a campaign hook the list does not write. Look at passenger and driver tags in Ptaxi’s ride-hailing app. If you want a walkthrough, ask for a demo and bring one rule you actually want to run, plus one case that should stay a manual static tag, then watch the tagged lists after both are applied.

Frequently asked questions

What is the difference between a dynamic tag and a static tag?

Dynamic tags are applied automatically when configured conditions are met. Static tags are applied manually by customer service in the backend. Both passenger tags and driver tags use this same structure. A dynamic tag stays current if the conditions are right. A static tag is precise on the day it is applied, and it rots if nobody maintains it.

Which condition fields can a dynamic tag use, such as spend or cancel rate?

The list confirms that conditions can be configured, but it does not name the fields. Do not treat spend, cancel rate, city, or any other attribute as a documented product fact. Operators will want to decide those conditions in a demo. Write down the fields the build actually offers, and brief the feature as configured conditions until you have seen that screen.

Are audience tags the same as rating tags?

No. Audience tags are people labels: tagging rules plus a list of tagged passengers or tagged drivers. Rating Tags is a different screen, used to configure rating tags, cancellation reasons, complaint reasons, and refund reasons. If a buyer asks about tags in a demo, open both screens and say which one you are training.

Can tags automatically target a reward campaign, change dispatch, or change price?

The list does not say audience tags automatically attach to reward campaigns, and it does not document tag-based automatic dispatch or tag-based pricing. Tags can help staff find an audience they want to think about. Reward campaigns remain a separate tool that users join in the app. Do not invent a passenger-facing page where a rider inspects or edits these labels.

Related articles

Ride-Hailing Pricing Plans: Base, Distance, Time, Long-Distance, and Waiting Fees

A ride-hailing estimate is only useful if it comes from the plan you actually configured. The admin Pricing Plan lets you set a base fare — starting fee or base fee — plus distance, time, long-distance, and waiting fees, with different unit prices by time period. You bind that plan to a vehicle tier and choose a cycle: weekdays, weekends, holidays, or a custom cycle, so the passenger’s estimated fare follows the same rules.

· 8 min read

Talk to our team about your platform

Tell us your market and business model. We will reply with a feature plan, a demo of the apps and a quote.