Japanese CRM systems need keigo-compliant email templates, company-department-contact hierarchy, and Salesforce configuration that matches the Japanese enterprise sales process

In Salesforce, the standard data model supports Account (company), Contact, and Opportunity (deal) objects, but does not natively support department as a distinct object with its own contact relationships. The most effective approach for Japanese enterprise sales is to use a custom object for Department that sits between the Account and Contact, with lookup relationships connecting all three. Each Contact record can then be tagged with their Department, their role type (担当者 or 決裁者), and their relationship to the active Opportunity. In HubSpot, a similar structure can be achieved using the standard Company and Contact objects with custom properties for department name, role type, and decision-making authority, along with multi-contact deal associations. Neither platform does this out of the box — it requires custom object configuration or property setup.

All automated emails sent to Japanese business contacts must use the formal honorific register (丁寧語 or 敬語 where appropriate). This applies to the opening salutation, the body copy, and the closing. Informal expressions, casual verb conjugations, and first-name addressing are all inappropriate in a Japanese business context. The email structure should follow Japanese business letter conventions: a seasonal or contextual opening (時候の挨拶), clear statement of purpose, the substantive content, and a formal closing. Auto-generated English templates translated by machine translation will routinely fail these requirements. Every CRM email template used in a Japanese-market system should be written by or reviewed by a native Japanese business communication professional before deployment.

LINE Business Connect provides an API that allows businesses to integrate their LINE Official Account with external systems including CRM platforms. For Salesforce, third-party connectors exist that log LINE messages against contact or opportunity records. For HubSpot, the integration requires either a custom API connection or a middleware tool such as Make or Zapier with a LINE connector. Standard LINE (consumer) does not expose an API for third-party integrations, so businesses need to migrate team communication to LINE for Work or use LINE Official Account as the business communication channel to enable CRM logging. The scope of what is logged depends on the integration — at minimum, message timestamps and content can be stored as activity records against the relevant deal.

Salesforce holds the largest share of the Japanese enterprise CRM market and is the most commonly deployed platform in large Japanese organisations. Local Japanese CRM alternatives include Cybozu's kintone (which has strong process customisation capability and a significant Japanese user base) and Sansan (which focuses on business card management and contact enrichment, reflecting the importance of meishi exchange in Japanese business culture). For SMBs, HubSpot and Zoho have growing adoption in Japan. The choice of platform is less important than whether it is configured to match Japanese sales process and communication requirements. A Salesforce instance configured for a US process is less useful to a Japanese team than a well-configured kintone or Zoho instance.

The adaptation process involves four areas. First, the deal stage logic needs to be rebuilt around the Japanese sales progression: initial introduction, relationship development, internal consensus building (nemawashi), formal proposal, procurement or legal review, contract execution, and onboarding. Second, all deal stage names and field labels need to be rewritten in natural Japanese business language, not literal translations of English terms. Third, the contact hierarchy needs to support multiple contacts per deal with role differentiation between 担当者 and 決裁者. Fourth, the activity logging and reporting configuration needs to reflect ほうれんそう practice — supporting regular status updates, escalation flags, and consultation notes as structured activity types, not just call logs and emails. This is a significant reconfiguration, not a cosmetic localisation.