Twitter Name: Now @CapMetroATX

Tweet, Tweet!

For those of you who follow our Twitter activity (or may want to), you may have noticed our recent change of account names.

In the past, we have communicated to followers using two separate Twitter accounts: CapMetroNews and CapMetroRail. Having two accounts made sense leading up to the opening of MetroRail, but now it’s just sort of confusing. People tweet us with rail-related inquiries at CapMetroNews and with bus issues at CapMetroRail. Plus, having two accounts sometimes contributes to a delay in us responding.

Going into our new fiscal year in October 1, we wanted to use that date as a benchmark for turning over a new leaf in our Communications efforts — including Twitter.

Going into the future, we have changed the name of our CapMetroRail account to @CapMetroATX. This will be our one and only account where we’ll provide bus and rail service updates as well as relevant news and rider tips. Over the next two weeks we’ll phase-out our CapMetroNews account.

We know by following one sole account, you may get more info than before. So, how can you filter the info you get notifications about, if you want?

By using certain apps, you can make settings to only get notified of certain hashtags, versus receiving all our Tweets.

We’ll be operating via these hashtags:

#MetroRailAlert: for specific delay alerts on MetroRail

#MetroBusAlert: for all bus-related service alerts

So, for example, if you began following our rail account and only wish to continue receiving rail-related messages, set-up your account to send only messages including the #MetroRailAlert hashtag.

How to set specific alerts up? This useful YouTube video helps you use TweetDeck for setting-up hashtag notifications:

If you’re not into Tweet Deck, there’s also Boxcar for push notifications as well.

This change may take some getting used to, but it’s for the better — to provide improved communications and customer service. So, jump right it, follow us at www.twitter.com/CapMetroATX.

Tweet you soon!
https://capmetroblog.com/tag/twitter/
capmetroblog.com
crawl=CC-MAIN-2022-27
93456
application/http; msgtype=response
sha1:QDLIKHOTMSWQNHILWCNAXKJ7Z65EW5JG
<urn:uuid:66e44aad-8ce6-4175-91a6-eff722b80b3a>
2022-06-27T02:35:13Z
192.0.78.25
text/html
sha1:QFYAFAAEGCBQFATIK7RU7VTBYD55VESM
<urn:uuid:8dc942d4-39ba-4b8e-ac58-f59445fa6a2f>
https://capmetroblog.com/tag/twitter/
response
<urn:uuid:91dc878b-a693-44db-9b68-985a5bb38ed1>
isPartOf: CC-MAIN-2022-27
publisher: Common Crawl
description: Wide crawl of the web for June/July 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-140
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.3-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/