A Guide to Choosing Cross-Border Network Services

Turn search terms into goals you can test

A search for “a good VPN” can reflect very different needs: browsing documents, joining remote meetings, using AI tools or watching video on a home TV. Each use case has different requirements for exit regions, connection stability, data use and client compatibility. Before comparing prices, note the apps you use most, when you use them, your network and your main devices.

Describe needs as specific actions. Instead of “fast speeds,” try “audio stays clear during meetings, and opening a shared document doesn’t interrupt the call.” Instead of “works with AI,” try “I can sign in, keep a session active and upload a file.” You can check these goals one by one during a trial and describe them clearly to support if something goes wrong. Vague feedback gets vague answers; specific tasks give you something concrete to assess.

Separate must-haves from acceptable trade-offs

Prioritize tasks you can’t afford to interrupt for work or study, and treat occasional regions or apps as secondary. A service may cover many regions yet still be a poor fit if your usual network has trouble reaching the exit you need. Conversely, a suitable primary exit and a useful backup for maintenance can matter more than a long list of regions you rarely use.

Consider where you’ll connect, too. Home broadband, office networks and mobile networks take different routes, so performance on one does not predict performance on another. Office networks may have management policies, and hotel Wi-Fi may require a web sign-in first. Test only on networks you’re authorized to use. Don’t blame the service route for problems caused by local access, and don’t keep changing unfamiliar system settings in the hope that something will work.

Consider your budget alongside how often you use it

If you regularly stream video, sync files or collaborate online, focus on whether the data allowance is sufficient and whether connections hold up at busy times. If you only look things up occasionally, consider how billing works when you’re not using the service. Don’t rank these use cases by price alone. Estimate how often you’ll use the service, then compare monthly plans with data packages to avoid choosing a billing model that doesn’t fit your routine just because it looks cheaper.

Your budget also includes the cost of switching. Reinstalling a client, moving device settings and learning to troubleshoot all take time. When comparing services, note whether the documentation is clear, the dashboard makes the subscription easy to find and the support process is straightforward. This isn’t about paying for a polished interface; it’s about whether you can diagnose a connection issue yourself or give support the right details.

Build a shortlist before reaching a conclusion

Use the same checklist for every candidate: billing model, data rules, device limits, supported clients, refund terms and support channels. Mark anything not publicly explained as “to confirm”; don’t fill in the gaps on the provider’s behalf. Missing public information doesn’t prove a feature is unavailable, but until it’s confirmed, don’t count it as an advantage. Leave room for uncertainty in your comparison.

VPNXM publicly lists coverage in 100+ countries and 250+ routes, supports Windows / macOS / iOS / Android / Linux, and allows unlimited simultaneous devices. These facts can help you assess coverage and platform compatibility, but they don’t show that every region suits every task. For more detail, check the route descriptions on the Servers page and test access from your own network.

Once you’ve written down your needs, you should be able to answer a simple question: if the test passes, which everyday task becomes possible? If it fails, which requirement wasn’t met? A clear answer keeps your comparisons of routes, bandwidth and plans focused on practical value instead of eye-catching specs or short-term promotions.

Look at the path, not just the route label

A cross-border connection usually involves your local access network, the service’s entry point, cross-border transit, an exit network and the destination website. A route label only summarizes some of these parts; it doesn’t describe the whole path. A nearby entry point doesn’t guarantee fast access from the exit to the destination. Nor does an exit in the right region guarantee a stable connection from your network to the entry point. When comparing routes, consider the local access leg separately from the connection to the destination.

An IEPL route generally means that an international Ethernet private line carries part of the traffic. This differs from direct routing over the public internet and involves costs for the provider’s line and access resources. But a route that “includes a dedicated segment” doesn’t mean every connection from your device to the destination uses a private channel, nor does it guarantee that the destination will always be available. The coverage of the dedicated segment, the entry point and the exit resources all affect the experience.

A relay is about how the route is arranged

A relay route sends your connection to an intermediate entry point before forwarding it to an overseas exit. Choosing the entry point well may improve local access or the cross-border path, but adds another network segment to maintain. A relay isn’t automatically slow just because it takes an extra hop: internet traffic doesn’t always follow geographic distance. But a relay isn’t automatically faster, either. Compare how well it completes your tasks on the same access network.

A direct route typically connects over the public internet to an overseas entry or exit, with a simpler path that’s more sensitive to public routing changes. When local conditions are favorable, direct routing may be enough for everyday use. Cross-border congestion or carrier routing changes can also cause fluctuations. Consider it as one possible route, not something to dismiss because the label sounds basic or assume is more reliable because it has fewer steps.

Cost differences don’t translate directly into a performance ranking

Service costs also include bandwidth, exit resources, equipment maintenance and support. A route label alone can’t tell you whether the price is reasonable. Services with the same stated architecture may organize entry points and manage capacity differently; different prices don’t necessarily mean performance differs by the same proportion. What you can test is how the service performs on your usual network, at your usual times and with your usual apps.

Dedicated, relay and direct routes can also be combined. A route might use a relay entry point and a dedicated line for cross-border transit, so these labels aren’t always mutually exclusive. When reading a service description, ask which part of the route each label refers to rather than ranking the labels mechanically. If a provider lists route names without explaining how to choose, note the uncertainty and decide after testing whether the resources are worth the cost.

Choose backup paths, not just regions to bookmark

A useful backup route should offer different path conditions. Routes with different names but the same entry or exit may be affected by the same maintenance. You usually can’t see all the underlying resources, so don’t assume routes are completely independent. A more practical approach is to record how each option performs on different networks, keep a primary and a backup, and check whether switching actually helps your task when a problem occurs.

Choose a region that also fits the target app’s regional requirements. An exit closer to you may respond faster, but the service you’re using may only offer a feature in a specific region. Apps that require sign-in may also consider account information; a route label can’t override the app’s own requirements. Don’t switch regions repeatedly just to chase lower latency. For ongoing sessions and important tasks, prioritize a stable exit that meets the app’s requirements.

To compare routes, start with a familiar region that connects successfully, then see whether a different architecture improves the problem. If every route fails on the same device, check your local network, system proxy and client settings. VPNXM’s route types and regional entry points are listed on the Servers page. These architecture descriptions help explain the options; they’re not performance guarantees for any specific route.

Peak throughput and responsiveness aren’t the same thing

Bandwidth describes transfer capacity; latency is the round-trip response time; jitter measures how much response times vary; and packet loss can trigger retransmissions and interrupt tasks. Downloads make throughput differences easy to spot, while remote meetings and interactive apps depend more on a steady response. A fast download in one speed test only describes the transfer to that test server at that moment. It doesn’t prove that every app, direction or time of day will perform the same way.

Distinguish your local broadband capacity, the service’s route capacity, performance on a single connection and limits imposed by the app’s server. Any one of these can become a bottleneck. A bandwidth label for a route doesn’t necessarily mean that each account gets a dedicated allocation. Unless the service clearly defines how capacity is measured, don’t treat total exit capacity as a personal guarantee or make a purchase decision based on a number beside a client icon.

Concurrency is about competition for resources

Concurrency isn’t just the number of devices; it also includes the apps and connections running at the same time on each device. Background sync, large downloads, video playback and meetings can compete for local upload and download capacity as well as the service’s exit resources. Even if a service allows unlimited devices, devices in a household still share network resources. When comparing concurrent use, check whether your usual tasks can run together—not just whether the client shows connected on each device.

Upload use is easy to overlook. Backups or video calls can consume local upload capacity and make other apps less responsive. If everything at home suddenly slows down, pause background uploads first and see whether meetings and web browsing recover. If they do, check your task schedule and local network instead of immediately switching overseas routes. Pinpointing the issue is more informative than repeatedly changing nodes.

Set up tests you can repeat

For each speed test, note the access network, client mode, route region, target app and approximate time. Test each candidate under conditions that are as similar as possible. Don’t test one service on an idle network and another while a background download is running. Browser and app caches, as well as existing connections, can affect results. After switching services, confirm that new requests are actually using the new route.

Start with your local network: check that your connection and local apps work without the service, then connect a candidate route and try the target app. Finally, add your usual background tasks and observe the effect. If the issue occurs only on Wi-Fi, test from a location with a stronger signal or cross-check on a wired connection. This helps separate Wi-Fi coverage and local congestion from cross-border route issues.

At peak times, check whether tasks finish reliably

At peak times, don’t judge performance by a single speed-test peak. Join a typical meeting, work in an online document for a while or stream the content you normally watch. See whether you have to reconnect repeatedly or lower the quality to keep going. For people who work online for extended periods, consistent performance often matters more than an occasional high peak. Test during your actual hours of use rather than picking the time that produces the best-looking result.

If the problem affects only one app, check its status, regional requirements and account prompts first. If all routes in one region are affected, compare other suitable exits. If every exit is affected, check your local network and client. Change one major condition at a time and note what happens before and after. Changing the mode, protocol and region all at once removes the basis for comparison and makes it harder to explain the issue to support.

Save test results as conditional findings, such as “Works for documents and meetings on home broadband; mobile network still needs testing.” Don’t present limited results as a long-term guarantee. For more on test tools, timing and metrics, see the VPN speed test guide. This page focuses on using those metrics to compare services, not replacing your judgment with a speed-test ranking.

Separate the billing period from the data allowance

When comparing plans, consider price, billing period, available data and reset rules together. A monthly plan suits ongoing use, while a data package can work better if your usage is intermittent and you want to pay based on consumption. Don’t decide based only on the total data or price. How regularly you use the service and whether your usage spans a reset date both affect the value you get.

VPNXM monthly plans are ¥9.9/month for 60GB, ¥18/month for 250GB and ¥28/month for 500GB. Data resets monthly on the activation date. When you upgrade mid-cycle, the price difference is converted into remaining days. “On the activation date” does not mean that data resets at the start of each calendar month, and unused data should not be assumed to roll over. Check your current plan and reset status in the dashboard before purchasing.

Choose based on actual usage, not an app’s label

“I mostly watch video” isn’t enough to estimate data use. Video quality, viewing time, automatic quality changes and background preloading all affect consumption. Online documents may also involve asset downloads and cloud sync. A more reliable approach is to check data usage in the dashboard during your usual routine and note what tasks you’re doing. Don’t assume an app is light or data-intensive based on its name alone.

For your first plan, set a budget around the tasks you already know you’ll do, then see how your usage develops before deciding whether to change plans. If you upgrade, check the actual result in the dashboard rather than estimating extra data or days from the price difference. VPNXM’s stated upgrade rule is that the price difference is converted into remaining days; it doesn’t imply any unannounced bonus, discount or other billing commitment.

“Never expires” describes the data package’s validity

VPNXM data packages are ¥158/300GB, ¥358/1000GB and ¥658/3000GB. They’re valid until used and never expire. Consider whether your usage is spread out and whether the cost fits your budget. “Never expires” doesn’t mean the price will never change, every feature will remain fixed forever or every app will always be available; those are separate matters.

If you’re considering both a monthly plan and a data package, first confirm whether the dashboard supports the combination you want and which allowance is used first. Don’t guess about stacking, priority or conversion rules that aren’t stated in the available details. A rule used by another service doesn’t necessarily apply here. If anything is unclear, note your question and confirm it through support before deciding.

Check your order and coverage before paying

Before paying, check the plan, amount, data and billing method shown in the order, and confirm they match what you just reviewed. VPNXM supports Alipay / WeChat Pay / USDT. A payment method is just a way to pay; it doesn’t mean you’ll get extra data or higher priority. If the order status is unclear after payment, check your dashboard’s order history before creating the same order again.

See the Pricing page for full plan details. VPNXM offers a 60-day no-questions-asked refund; read the Terms of Service for the applicable terms. A refund policy can reduce uncertainty when choosing for the first time, but it doesn’t replace assessing your needs. Test your everyday tasks soon after purchase rather than waiting until you need the service to find out that a platform or route isn’t a good fit.

When comparing providers, record their billing details in the same format instead of comparing a monthly plan’s one-month price directly with the total cost of a data package. Consistent terms make it easier to see whether you’re weighing recurring costs or spending tied to data use. There’s no billing model that suits everyone; the right choice depends on your current usage.

Unlimited devices doesn’t mean unlimited resources

VPNXM allows unlimited simultaneous devices, which can suit people who switch between a computer, tablet and other supported devices. This removes a device-count limit; it doesn’t give each device its own data allowance or make local broadband and exit capacity immune to demand. When household members stream, upload files or join meetings at the same time, plan around your data allowance and actual network conditions.

Device sharing also involves account boundaries. Using a subscription across your own devices isn’t the same as sharing it with people you don’t know. Subscription settings can grant access, so protect them like account credentials. At home, agree on who maintains the client, handles plan changes and reports problems. Otherwise, everyone may change settings at once, making it hard to tell what caused the connection to change.

A platform list doesn’t guarantee a straightforward setup

VPNXM supports Windows / macOS / iOS / Android / Linux. Platform support means there’s an applicable way to connect, but system permissions, installation sources, network policies and device settings can still affect use. A work-managed computer may restrict installations or proxy changes, and home devices may have other networking tools running. Before choosing a service, check that you’re allowed to install it and whether other software could conflict.

On platforms other than iOS, you can download the client after signing in; the iOS access link requires an active plan. Sign in to get your subscription; installation packages aren’t linked directly from marketing pages. Get the relevant files from the client section of the user dashboard, rather than judging the source by a similar-looking filename in search results. Follow the Guides for setup, and don’t reuse configuration from another service.

Test a representative device before adding more

For a home setup, test your usual tasks on a familiar device first, then add other platforms. If something differs, you can compare whether the cause is the account, route or platform settings. Importing the settings and changing them on every device at once can muddle the evidence. After a representative device passes, note its route and mode, then repeat the same tasks on each new device to pinpoint platform differences.

If a desktop browser works but another app doesn’t, the app may not follow the system proxy. If a mobile connection changes when the screen locks, background management could be involved. These symptoms don’t automatically mean the plan is incompatible. Check that the client is still running, the system hasn’t revoked permissions and the app is using the expected route. Don’t disable system protections or change numerous network settings without understanding the consequences.

For home sharing, manage data use and account access

Household members may have very different usage habits. Consider scheduling large syncs and downloads around important meetings, and keep an eye on data use in the dashboard. If consumption suddenly rises, check background backups, autoplay and newly added devices before assuming someone else has accessed the account. If the device list and tasks don’t explain the change, then check whether credentials may have been shared in a screenshot, chat or public document.

VPNXM doesn’t require an email address; you can create an account with a username and password. Keep your credentials safe and avoid reusing the same password across unrelated sites. Providing less information doesn’t mean account security can be ignored. Follow the recovery and support options actually available in the dashboard rather than assuming there are unpublished ways to regain access.

When you pass on a device, reinstall its operating system or stop using it as a household member, remove the client configuration from the old device and check whether the subscription needs updating. When contacting support, you can include the platform, error message and steps you’ve tried, but hide your subscription details and password. For more security advice, see the Security Guide for Beginners. Unlimited devices are most useful when everyone knows who is responsible for maintaining them.

A network connection is only the first step toward using an app

Being able to open a website doesn’t mean you can sign in, upload, stream and interact continuously. Apps may check the exit region, account details, payment region, browser state and their own risk controls. Test the complete task, not just whether the home page loads. For services that require an account, follow the platform’s usage requirements; changing routes doesn’t resolve every account restriction.

Build your test around things you actually do each day: open a familiar document, submit a request of the usual length, upload a suitable work file or join a regular collaboration session. Avoid using files with sensitive information, and confirm you’re allowed to upload them to the target platform. This lets you test connection stability without sending confidential material to a service you don’t know well.

AI tools need a reliable session

When using tools such as ChatGPT, Claude and Gemini, check more than whether the page opens: make sure you can stay signed in, receive a complete response and upload files without interruption. Some issues come from the service or your account permissions, not the network route. Read the specific error message before testing another path; don’t assume every failure is caused by the exit.

For ongoing use, choose an exit that meets the target service’s regional requirements and avoid switching regions without a reason. Frequent changes to your access environment can lead to more account checks and make issues harder to diagnose, but keeping the same region doesn’t guarantee account security. If a sign-in prompt changes, note the relevant error, check your account status and compare it with other network behavior. Don’t hand over your credentials to a third party to maintain a session for you.

For practical route-selection advice for AI use, see the AI Access Guide and the guide to comparing ChatGPT sign-up, login and ongoing use. These comparison methods are for your own testing; they don’t mean VPNXM guarantees permanent access to every AI platform. Platform policies and how they identify exit routes can change, so check results against your current tasks.

When testing video, separate playback from content access

Video problems can arise from content permissions, regional detection, account plans, the player or the content delivery network. If you can open a site but can’t watch a particular title, the issue may not be transfer capacity. If playback starts but buffers repeatedly, check the route and your local network. When comparing services, note the specific error or playback behavior instead of simply writing “streaming doesn’t work.”

Picture quality also depends on your device, display settings, the content itself and app policies. Automatic quality may drop to keep playback going, and a browser may behave differently from a native app. Test with the devices and playback methods you normally use, and watch long enough to spot buffering. A smooth preview clip doesn’t tell you how a full viewing session will go.

For work apps, test uploads and reconnection

Online meetings, code collaboration and cloud editing often rely on different network requests at the same time. A page loading doesn’t mean the real-time call or file-sync route is working. On a network you’re authorized to use, test joining a meeting, sharing content, uploading a file and recovering from a dropped connection. Check whether switching networks prompts another sign-in or loses work. Keeping an appropriate local copy of important work is better than guessing about connection status later.

If only one app is affected, check whether it follows the client’s current mode, then compare its behavior with a browser. If closing other networking tools fixes the issue, check for a proxy conflict. If changing access networks fixes it, focus on the local network. If changing exits helps, record which region and route conditions made a difference rather than simply labeling a route “good.”

Your final assessment should be specific about scope: which apps worked, on which devices and networks, and what still needs checking. If the target platform has a temporary outage, retest once it’s back rather than judging the entire service. The aim isn’t to produce an exaggerated claim that a service works for everything; it’s to confirm that your most important everyday tasks work under acceptable conditions.

Look for terms you can actually verify

Check refund terms and support channels before you buy, not only after something goes wrong. When comparing services, see whether refund statements match the formal terms, whether you can find orders and support tickets in the dashboard, and whether submissions are tracked. A prominent refund badge is only a summary. Read the relevant page for the actual scope and process; don’t stretch a short promotional claim into extra promises.

VPNXM offers a 60-day no-questions-asked refund; see the Terms of Service for the relevant rules. This guide explains how to compare and verify a service; it doesn’t replace the formal terms. A refund policy can be one factor in your comparison, but it doesn’t guarantee that a route will always work or make platform compatibility and your needs irrelevant. Test the service soon after purchase so you can assess the fit and prepare clear details if you need to make a request.

Handle order issues separately from connection issues

For an order issue, give the plan name, order status in the dashboard and payment result. Don’t send an entire payment-account page, unrelated transactions or personal details. If the displayed status hasn’t caught up, check the order history and on-screen messages before contacting support. Don’t create repeated orders to guess whether payment went through, and don’t follow unofficial chat instructions to pay an unfamiliar recipient.

Connection issues need different details: device platform, network, route name, current client mode, error message and the task you were doing. Instead of “it doesn’t work,” write “The client shows connected; I can open documents in my browser, but file uploads keep failing.” That gives support a starting point. Separate what you observed from what you suspect so troubleshooting doesn’t start from an unverified conclusion.

Give support enough detail without exposing credentials

Before submitting a ticket, list the steps you’ve tried in order: whether you changed access networks, paused background tasks, tested another suitable exit and what happened after each change. A ticket doesn’t need to be a technical report, but it should make the current state clear. If the issue is resolved, note what action fixed it to help determine whether the cause was a temporary fluctuation or a configuration conflict.

Example ticket: Using macOS on home broadband. Document browsing works, but uploads are interrupted. The issue still occurs after pausing background sync; uploads complete after switching to another suitable region. Screenshots have been edited to hide account and subscription details. Please advise what to check next.

Don’t post subscription details in public reviews, community threads or unfamiliar chat windows. Even when sending a screenshot to support, check whether the address bar, QR codes, configuration lists or logs contain access credentials. If diagnostic information is needed, use the official channel and follow its specific instructions; share only what’s necessary. Full logs aren’t always more useful, and removing unrelated sensitive information matters too.

Security messaging doesn’t replace account protection

VPNXM’s primary security claim is military-grade encryption. Encryption protects the relevant part of data transmission; it doesn’t remove a destination website’s verification requirements, protect devices from malware or make every website risk-free for privacy. Check website addresses, manage app permissions, protect your password and don’t let someone you don’t know configure your account. Route protection and device security are separate concerns.

Before choosing a service, read the Privacy Policy to learn how account and service-related information is handled. Don’t infer retention periods, audit findings or data-handling practices that the policy doesn’t state. VPNXM doesn’t require an email address; that’s a fact about the information needed to create an account. It doesn’t mean you can use every destination website without an account or that payment won’t generate an order record.

Assess support by how it handles requests, not guessed response times

Clear documentation, a visible support channel and coherent ticket history can make it easier to get help, but they don’t establish an unpublished response time. Don’t add round-the-clock support or fixed resolution deadlines to any provider’s claims. Check whether the help content explains common issues, the ticket form tells you what to include and follow-up replies address the symptoms you’ve already reported.

VPNXM support is available through tickets in the user dashboard. You can also check the FAQ for common questions. More useful than a vague promise to “fix everything” is support that distinguishes service issues from local conditions and third-party app policies, and explains what to verify next when more information is needed.

Identify capacity issues without equating every fluctuation with overselling

When a service repeatedly slows down at times you use it, it’s easy to suspect overselling. Similar symptoms can also come from local congestion, cross-border routing changes or a problem with the destination app. Compare conditions: do other services work on the same network, does another suitable exit help, does pausing background tasks make a difference, and does the issue recur under similar circumstances? Keep records of what happens to narrow down the possibilities.

If multiple suitable exits repeatedly interrupt tasks at the same peak times, while checks indicate that your local network and the target service are working normally, that’s a reasonable basis to ask support about capacity and maintenance. It still doesn’t directly prove what’s happening with the underlying resources. Look for practical alternatives, acknowledgment of known issues and whether performance improves later. Don’t draw a permanent conclusion from one speed-test screenshot, but don’t ignore a pattern that keeps recurring.

Interpret node counts in terms of what you can use

Node count, route count, region count and the number of independent exits aren’t interchangeable. One entry point may offer multiple configuration names, and multiple routes may share some resources. When you see a long list, first check how items are counted, then see how many suit your regions and apps. Different names don’t prove the resources are independent, and similar exits don’t prove the list is misleading.

VPNXM publicly lists coverage in 100+ countries and 250+ routes. This describes the range of options, not identical performance on every local network or availability of every app in every region. Start with the regions you use and suitable backups, then explore the rest if needed. The numbers can help narrow your choices, but they don’t replace client compatibility checks, route testing or a review of support terms.

Assess service continuity using verifiable facts

It’s reasonable to worry that a service could shut down, but a brand name, polished website or verbal assurance can’t eliminate that uncertainty. More practical signals include consistent public information, clear plan rules, matching entitlements in your dashboard after payment and a traceable support channel. If these basics are missing, pause and ask for clarification rather than paying more in search of reassurance.

Treat unverified third-party reviews as personal experiences, not necessarily repeatable facts. Positive reports may come from different regions and networks; complaints may involve different apps and conditions. Give more weight to accounts that describe their setup, tasks and troubleshooting, and be cautious of rankings without those details. Apply the same standard to every candidate: don’t skip testing because of one glowing review or rule a service out based on one vague complaint.

Keep confirmed facts separate from items to verify

Your final notes don’t need a complex score. Mark each item “meets expectations,” “doesn’t meet expectations” or “to confirm,” with the conditions and observations. If a critical task fails, don’t let minor advantages or attractive specs hide the problem. If only a secondary region needs checking, you can decide whether that trade-off is acceptable. A single subjective score can average away major drawbacks and make a comparison look more precise than it is.

For VPNXM, start by recording the known facts: monthly plan and data package prices are public, simultaneous devices are unlimited, supported platforms are listed, the refund period is 60 days and an email address isn’t required. Keep routes and apps you haven’t tested in the “to confirm” column. Separating published facts from personal experience avoids expecting things the service hasn’t promised and makes comparisons fairer and easier to review.

Reassess your needs after purchase

Choosing a service isn’t a once-and-for-all conclusion based on one test. Your location, access network, usual apps and home devices can change, so revisit the relevant conditions when your needs do. Keeping one suitable exit and clear troubleshooting notes is more useful than constantly chasing route names. To change plans, check the rules on the Pricing page; to install the client, follow the Guides.

Choose a service whose rules are clear, whose costs fit your budget and that completes your main tasks under your everyday conditions. Don’t focus on having every spec at the expense of your actual usage, or accept a billing arrangement you don’t understand just to spend less upfront. Note your needs, check the facts, then test the service. That process is a better basis for long-term decisions than relying on a “recommended” label.