Support for PulseTier is handled through support@weforce.store. Customers should include enough order and product detail for the team to identify the request without unnecessary back-and-forth.
Support channels
Email support
Primary support email: support@weforce.store. Use this address for product questions, shipping updates, return requests, warranty questions, privacy requests, and order assistance.
Support hours are Monday to Saturday, 09:00 to 18:00 HKT. Messages received outside support hours are reviewed during the next business support window.
Response target
The normal response target is within 1 business day for product, shipping, return, warranty, and order questions.
High-volume retail periods, carrier interruptions, address verification, supplier checks, or incomplete request details may require more time.
What support can help with
Pre-order and product questions
Support can help compare models, confirm broad compatibility points, explain product page specifications, and point customers to relevant policy pages.
For product support, include the product name, model number, photos if relevant, and a short issue summary.
Order and return questions
For order support, include the order email, product name, delivery address region, and the question or issue to be reviewed.
For return support, contact us before sending items back so eligibility, return address, packaging requirements, and timing can be reviewed.
Support handling logic
Information needed
The team may request order identifiers, product photos, packaging condition, carrier status, or address confirmation when needed to review a case.
Customers should not send payment card numbers or unnecessary sensitive documents through general support email.
Definitions, scope, and reading order
How this policy should be read
This contact us is written to explain how PulseTier handles ordinary customer situations, unusual review cases, and requests that require support judgment. It should be read together with the product listing, checkout information, account notices, support messages, delivery information, return instructions, privacy disclosures, and any product-specific notes shown before an order request is submitted.
If two documents appear to cover the same issue, PulseTier will normally read the more specific product, checkout, or support instruction together with this policy rather than treating one short sentence as the entire rule. The purpose is to preserve a practical record of what the customer saw, what information was available, and what operational route applies to the request.
Customers should contact support@weforce.store when a situation does not fit neatly inside the published examples. Support may ask for order details, product names, shipment context, photos, screenshots, device information, or other reasonable evidence before confirming how this policy applies.
Key terms used in this document
References to the store, site, catalog, checkout, account tools, product pages, support team, or customer service generally refer to PulseTier's customer-facing shopping experience and the support routes connected with it. References to a customer mean the person who browses, submits an order request, contacts support, or receives a product through the order information provided.
References to a product listing include the title, image, price, compare-at price, model reference, product category, specification table, shipping origin, warranty note, customer review area, related items, and any compatibility or fit guidance shown on the page. These elements are intended to work together rather than as isolated statements.
References to business days generally exclude weekends, public holidays, carrier closure periods, supplier closure periods, severe disruption periods, and days on which support cannot reasonably obtain information from a carrier, supplier, payment processor, or customer.
Customer responsibilities and information accuracy
Accurate order and contact information
Customers are responsible for submitting accurate contact details, delivery information, product choices, and account information when using PulseTier. Incorrect names, incomplete addresses, unsupported postal formats, unavailable phone numbers, or mismatched order details may delay processing, carrier handoff, return review, refund review, or support response.
When a customer submits checkout or support information, the store may reasonably rely on that information until the customer corrects it through a support request or account update. If a correction arrives after packing, dispatch, carrier handoff, refund initiation, or case closure, the available resolution may be narrower than it would have been before that operational step occurred.
Customers should use support@weforce.store to report mistakes promptly. Support may not be able to change a shipment, return route, billing record, privacy request, or case decision after the relevant process has already moved beyond the point where the information can be safely changed.
Evidence and documentation standards
A support request is easier to review when the customer provides a clear description, product name, order email, relevant dates, carrier status, photographs if the physical product is involved, screenshots if the issue relates to the site, and a preferred outcome. Evidence should be truthful, current, and connected to the specific product or request.
Photos should show the whole item, the affected area, packaging, label, accessory set, model reference, and any visible damage or discrepancy when relevant. Screenshots should include enough page context for the support team to identify the product, policy, message, or checkout state involved in the request.
If evidence is incomplete, inconsistent, unreadable, altered, unrelated, or does not match the order information, support may ask for clarification or may decide the request based on the information available. This does not mean the request is automatically rejected; it means the review must be tied to a reliable operational record.
Support review workflow
Initial triage
Support first reviews whether the request belongs under this contact us, another policy page, a product listing instruction, a carrier process, a payment process, or an account-support process. That triage step helps route the request correctly and prevents a customer from being sent through the wrong procedure.
The first response may ask for missing order details, confirm the issue category, explain the next evidence needed, or identify a practical support route. A first response is not always a final decision, especially when the request requires carrier records, supplier confirmation, payment review, fraud review, privacy verification, or product inspection.
Customers should keep the product, packaging, accessories, labels, messages, carrier proof, and relevant account records until the case is resolved. Discarding these materials before support review may limit the ability to verify a claim or complete the requested resolution.
Case review and decision logic
When PulseTier reviews a case, it may consider the product listing, checkout details, support messages, timing of the request, customer-provided evidence, previous account activity, carrier information, supplier constraints, payment status, product condition, and whether a requested outcome is operationally available.
A case may result in information only, order correction, carrier follow-up, replacement review, refund review, exchange review, privacy handling, account assistance, product guidance, or closure when the request falls outside the policy. Similar cases may have different outcomes if timing, evidence, product condition, route, or customer information differs.
Support decisions should be practical and documented. If a customer disagrees with a decision, the customer may reply with additional relevant information, but repeated messages that do not add new facts may not change the outcome.
Operational limits and third-party dependencies
Carrier, supplier, payment, and platform limits
Some parts of the customer experience depend on third parties that PulseTier does not fully control, including carriers, warehouses, suppliers, product manufacturers, payment processors, email providers, analytics providers, security tools, and customer devices or browsers.
The store will use reasonable support steps when a third-party route affects a customer request, but it may not be able to force a carrier scan, accelerate customs review, reverse a payment-processor hold, change a manufacturer warranty decision, or recover browser data deleted from a customer's own device.
If a third-party process has its own terms, privacy notice, timing, or verification requirement, the customer may need to follow that process in addition to contacting store support. The store will not treat every third-party delay or refusal as proof of store error.
Service continuity and exceptional events
Operational timing may be affected by severe weather, carrier disruption, supplier closure, network interruption, security incident, payment review, customs examination, regulatory requirement, public holiday, address verification, or unusually high request volume.
When exceptional events affect a request, support may prioritize safety, fraud prevention, data protection, carrier instructions, legal obligations, and the ability to maintain accurate records. This may change the timing or sequence of ordinary handling steps.
Customers should continue to use support@weforce.store as the main route for updates so the communication history remains connected to the case.
Records, privacy, and communication practices
Support records
PulseTier may keep support messages, order metadata, product references, carrier notes, privacy request records, return authorization details, refund notes, and account-support notes for a reasonable period needed to operate the store, resolve disputes, detect misuse, and comply with applicable operational requirements.
Support records should contain the information needed to handle the request and should not include unnecessary sensitive information. Customers should avoid sending payment card numbers, passwords, unrelated identity documents, or private information that is not needed for the case.
If a customer needs access, correction, deletion, or clarification of support records, the customer should use the privacy or contact route published on the site and provide enough information for the relevant record to be found.
Communication format
Store communication may occur by email, site notices, account messages, checkout notices, policy updates, or support replies. Customers are responsible for checking the email address and contact route they provided, including spam or filtering settings that may block ordinary support messages.
Support may summarize policy outcomes in practical language rather than repeating the full policy text in every reply. A short support reply should still be read together with the complete policy page and the facts of the case.
If a customer requests an urgent outcome, the request should clearly identify the urgency and the reason. Urgent language alone may not override product status, carrier status, privacy verification, fraud review, or payment timing.
Misuse, fairness, and exception handling
Misuse and inconsistent requests
PulseTier may limit, pause, or deny requests that appear fraudulent, abusive, inconsistent with the order record, based on altered evidence, intended to bypass a product condition, or designed to obtain an unfair advantage over ordinary customers.
Examples may include repeated false damage claims, conflicting delivery statements, attempts to return different goods, misuse of support staff, requests to change records after a dispute has begun, or attempts to avoid published checkout or policy conditions.
A misuse review should not prevent genuine customers from receiving help. It simply allows support to ask for evidence, compare records, and protect the store, carriers, suppliers, and other customers from unreliable claims.
Exceptions and goodwill handling
Support may occasionally offer a goodwill adjustment, alternate route, partial resolution, additional explanation, or extended review when the facts justify it. A goodwill action in one case does not create a permanent entitlement for every customer or every later case.
Exceptions are more likely when the customer contacts support promptly, provides reliable evidence, keeps packaging and accessories, communicates clearly, and asks for a realistic outcome. Exceptions are less likely when timing has expired, evidence is missing, the item is altered, or the request conflicts with carrier, supplier, payment, privacy, or safety requirements.
Any exception should be confirmed by PulseTier support in writing before the customer relies on it.
Policy updates and ongoing interpretation
Updates to this policy
PulseTier may update this contact us as product categories, support procedures, carrier routes, customer tools, legal obligations, marketplace practices, or risk controls change. Updated language generally applies to new browsing, order requests, and support interactions after the update appears on the site.
Older support cases may be reviewed using the policy, product listing, checkout information, and support messages that were available when the relevant event occurred, unless a later update is clearly intended to apply to ongoing cases.
Customers should review policy pages periodically, especially before placing a new order request or starting a return, privacy, delivery, or account-support process.
No waiver by silence or delay
If the store does not enforce a policy term immediately, that does not mean the term has been waived. Operational delay, investigation time, or a courtesy response does not remove the store's ability to apply the policy later when the facts are complete.
Likewise, a customer delay in replying may limit available options if a carrier, supplier, payment processor, return window, privacy verification period, or product condition changes before the case can be completed.
The best way to preserve options is to contact support@weforce.store promptly and keep the case information organized.
Definitions, scope, and reading order
How this policy should be read
This contact us is written to explain how PulseTier handles ordinary customer situations, unusual review cases, and requests that require support judgment. It should be read together with the product listing, checkout information, account notices, support messages, delivery information, return instructions, privacy disclosures, and any product-specific notes shown before an order request is submitted.
If two documents appear to cover the same issue, PulseTier will normally read the more specific product, checkout, or support instruction together with this policy rather than treating one short sentence as the entire rule. The purpose is to preserve a practical record of what the customer saw, what information was available, and what operational route applies to the request.
Customers should contact support@weforce.store when a situation does not fit neatly inside the published examples. Support may ask for order details, product names, shipment context, photos, screenshots, device information, or other reasonable evidence before confirming how this policy applies.
Key terms used in this document
References to the store, site, catalog, checkout, account tools, product pages, support team, or customer service generally refer to PulseTier's customer-facing shopping experience and the support routes connected with it. References to a customer mean the person who browses, submits an order request, contacts support, or receives a product through the order information provided.
References to a product listing include the title, image, price, compare-at price, model reference, product category, specification table, shipping origin, warranty note, customer review area, related items, and any compatibility or fit guidance shown on the page. These elements are intended to work together rather than as isolated statements.
References to business days generally exclude weekends, public holidays, carrier closure periods, supplier closure periods, severe disruption periods, and days on which support cannot reasonably obtain information from a carrier, supplier, payment processor, or customer.
Customer responsibilities and information accuracy
Accurate order and contact information
Customers are responsible for submitting accurate contact details, delivery information, product choices, and account information when using PulseTier. Incorrect names, incomplete addresses, unsupported postal formats, unavailable phone numbers, or mismatched order details may delay processing, carrier handoff, return review, refund review, or support response.
When a customer submits checkout or support information, the store may reasonably rely on that information until the customer corrects it through a support request or account update. If a correction arrives after packing, dispatch, carrier handoff, refund initiation, or case closure, the available resolution may be narrower than it would have been before that operational step occurred.
Customers should use support@weforce.store to report mistakes promptly. Support may not be able to change a shipment, return route, billing record, privacy request, or case decision after the relevant process has already moved beyond the point where the information can be safely changed.
Evidence and documentation standards
A support request is easier to review when the customer provides a clear description, product name, order email, relevant dates, carrier status, photographs if the physical product is involved, screenshots if the issue relates to the site, and a preferred outcome. Evidence should be truthful, current, and connected to the specific product or request.
Photos should show the whole item, the affected area, packaging, label, accessory set, model reference, and any visible damage or discrepancy when relevant. Screenshots should include enough page context for the support team to identify the product, policy, message, or checkout state involved in the request.
If evidence is incomplete, inconsistent, unreadable, altered, unrelated, or does not match the order information, support may ask for clarification or may decide the request based on the information available. This does not mean the request is automatically rejected; it means the review must be tied to a reliable operational record.
Support review workflow
Initial triage
Support first reviews whether the request belongs under this contact us, another policy page, a product listing instruction, a carrier process, a payment process, or an account-support process. That triage step helps route the request correctly and prevents a customer from being sent through the wrong procedure.
The first response may ask for missing order details, confirm the issue category, explain the next evidence needed, or identify a practical support route. A first response is not always a final decision, especially when the request requires carrier records, supplier confirmation, payment review, fraud review, privacy verification, or product inspection.
Customers should keep the product, packaging, accessories, labels, messages, carrier proof, and relevant account records until the case is resolved. Discarding these materials before support review may limit the ability to verify a claim or complete the requested resolution.
Case review and decision logic
When PulseTier reviews a case, it may consider the product listing, checkout details, support messages, timing of the request, customer-provided evidence, previous account activity, carrier information, supplier constraints, payment status, product condition, and whether a requested outcome is operationally available.
A case may result in information only, order correction, carrier follow-up, replacement review, refund review, exchange review, privacy handling, account assistance, product guidance, or closure when the request falls outside the policy. Similar cases may have different outcomes if timing, evidence, product condition, route, or customer information differs.
Support decisions should be practical and documented. If a customer disagrees with a decision, the customer may reply with additional relevant information, but repeated messages that do not add new facts may not change the outcome.
Operational limits and third-party dependencies
Carrier, supplier, payment, and platform limits
Some parts of the customer experience depend on third parties that PulseTier does not fully control, including carriers, warehouses, suppliers, product manufacturers, payment processors, email providers, analytics providers, security tools, and customer devices or browsers.
The store will use reasonable support steps when a third-party route affects a customer request, but it may not be able to force a carrier scan, accelerate customs review, reverse a payment-processor hold, change a manufacturer warranty decision, or recover browser data deleted from a customer's own device.
If a third-party process has its own terms, privacy notice, timing, or verification requirement, the customer may need to follow that process in addition to contacting store support. The store will not treat every third-party delay or refusal as proof of store error.
Service continuity and exceptional events
Operational timing may be affected by severe weather, carrier disruption, supplier closure, network interruption, security incident, payment review, customs examination, regulatory requirement, public holiday, address verification, or unusually high request volume.
When exceptional events affect a request, support may prioritize safety, fraud prevention, data protection, carrier instructions, legal obligations, and the ability to maintain accurate records. This may change the timing or sequence of ordinary handling steps.
Customers should continue to use support@weforce.store as the main route for updates so the communication history remains connected to the case.
Records, privacy, and communication practices
Support records
PulseTier may keep support messages, order metadata, product references, carrier notes, privacy request records, return authorization details, refund notes, and account-support notes for a reasonable period needed to operate the store, resolve disputes, detect misuse, and comply with applicable operational requirements.
Support records should contain the information needed to handle the request and should not include unnecessary sensitive information. Customers should avoid sending payment card numbers, passwords, unrelated identity documents, or private information that is not needed for the case.
If a customer needs access, correction, deletion, or clarification of support records, the customer should use the privacy or contact route published on the site and provide enough information for the relevant record to be found.
Communication format
Store communication may occur by email, site notices, account messages, checkout notices, policy updates, or support replies. Customers are responsible for checking the email address and contact route they provided, including spam or filtering settings that may block ordinary support messages.
Support may summarize policy outcomes in practical language rather than repeating the full policy text in every reply. A short support reply should still be read together with the complete policy page and the facts of the case.
If a customer requests an urgent outcome, the request should clearly identify the urgency and the reason. Urgent language alone may not override product status, carrier status, privacy verification, fraud review, or payment timing.