Skip to main content

Using Tags

Tags help you customize Beeline Routes to your specific business needs.

Jen Davies avatar
Written by Jen Davies
Updated over 6 months ago

Summary

Beeline Routes supports several customizations to get our system to work for your specific business needs. In this article, we’ll go over what we can do with tags.

You can tag jobs as well as customers. We treat them the same. Tags are not case sensitive; "anytime" is the same as "ANYTIME".

Arrival Windows

You can use tags to tell us about arrival windows, so even when you check the box to 'Ignore Target Arrival Windows', we'll still make sure the jobs happen in the windows defined by the tags.

Examples:

8am

8-9am

10am-12pm

10-1pm

morning

afternoon

evening

morning is 8am-12pm, afternoon is 12pm-4pm, and evening is 4pm-8pm

You can also tag a job as "any time", "anytime". This causes Beeline to do that job at any time of the day, even when you don't check the box to 'Ignore Target Arrival Windows'

Or the opposite as above, you can tag a job as “Don’t Move”, and that will cause our system to use the arrival window defined in your CRM, even though you check the box to ‘Ignore Target Arrival Windows’

Job Duration

You can also use duration tags. By default we use the duration of the job as defined in the CRM. However you can override that by providing Beeline with tags. For Housecall users, unscheduled jobs don't have a duration, so these duration tags become more important to set. Especially if some unscheduled jobs have different durations.

Examples:

30 minutes

30 minute

30 min

30minutes

30mins

2hour

2hrs

2 hours

Crew Members

You can also tag jobs as "same crew", "samecrew", "same tech". This means that even if you check the box to 'Move Jobs Between Crew' we'll make sure that the currently assigned crew member in your CRM stays as the assigned person for the job.

You can also tag a job as "any crew", "anycrew". This will allow beeline to move that job between crew members even when you don't check the box 'Move Jobs Between Crew'.

Absolutes

We support Priority jobs as well. This ensures that the job(s) are always first in the route, just let me know what tag word you want to use for that. Some classics are "First", "Priority", "ASAP", etc. I add these manually to your account, whichever tag you'd like us to use.

We also support Last as well. This ensures the job(s) always happen last in the route. Again just let us know what you’d like to use as a tag for that. Some classics are “Last”, “Final”, etc.

Did this answer your question?