Multi-agent cooperative marketing digital employee interaction method

Abstract

This invention discloses a multi-agent collaborative marketing digital employee interaction method, specifically relating to the field of intelligent marketing interaction technology. It addresses the problems of inconsistent interaction content between successive rounds of marketing in existing multi-entity, multi-channel continuous marketing processes, including repeated triggering of confirmed items and disconnects between different executing entities. By aggregating channel interaction records, manual processing records, and business confirmation records to generate a continuous marketing session ledger, it extracts the current marketing stage, current channel status, current receiving entity, confirmed items, prohibited duplicate inquiries, and pending items to form a receiving constraint record. The method then verifies the receiving qualifications of the marketing digital employees to be executed before executing the marketing interaction according to the constraints. This ensures consistent receiving interfaces between successive rounds of marketing, avoids duplicate inquiries, prevents repeated triggering of confirmed items, and prevents disconnects between different channels and entities.

Description

Technical Field

[0001] This invention relates to the field of intelligent marketing interaction technology, specifically to a multi-agent collaborative marketing digital employee interaction method. Background Technology

[0002] When enterprises reach out to customers through channels such as SMS, social media messaging, outbound calls, and website inquiries, they typically already have basic systems in place, including customer profiles, channel records, manual follow-up records, and order or appointment confirmation records. These systems can handle individual actions such as message sending, manual processing, result registration, and business confirmation. In some scenarios where digital marketing staff have been introduced, different automated outreach entities are already handling tasks such as initial outreach, reminder pushes, event notifications, and appointment guidance, while human agents or operations personnel continue to intervene in customer inquiries, exception follow-ups, and confirmation registration. On the surface, existing systems can cover the basic link of "record collection - customer outreach - result registration," but these records are often scattered across different channels, business pages, and internal processing pages. The recording criteria, time bases, and boundaries are not consistent. They are mostly recorded separately for single outreach, single follow-up, or single business page, lacking unified organization and continuous connection for the continuous marketing process around the same target customer.

[0003] Furthermore, in multi-channel, multi-entity continuous marketing scenarios, existing practices typically focus more on single-point results such as "whether there was contact," "whether there was a response," and "whether there was confirmation," while lacking unified constraints on the continuity between multiple rounds of interaction. Although interaction records, manual processing records, and business confirmation records generated by different channels objectively exist, they are often not organized into a unified, continuously accessible conversation chain. When marketing digital staff enter the next round of interaction, they often can only read partial records from the current channel, or rely on simple tags, static lists, or manual notes to determine whether to continue contacting, making it difficult to accurately identify the current marketing stage, the current channel status, the current receiving entity, which matters have been confirmed, which matters should not be asked repeatedly, and which matters still need to be advanced. As a result, situations easily arise where matters confirmed in the previous round are asked again in the next round, content that has been explained in the previous channel is repeatedly triggered in another channel, customers who have been manually contacted are contacted again by the automated entity, or the customer status has progressed while subsequent interaction content remains at the previous stage.

[0004] Therefore, the more prominent practical problem in existing technologies is not that a single channel cannot reach customers, nor that a single entity cannot execute marketing actions, but rather that in the continuous marketing process targeting the same customer, there is a lack of a processing mechanism that can merge and organize records from multiple sources around a unified conversation link, continuously extract the current customer engagement status, constrain the scope of subsequent engagement, and verify the eligibility of marketing digital employees before execution. This leads to inconsistent engagement interfaces between different entities in collaborative marketing, repeated triggering of confirmed matters, and disconnection between different channels and entities, thereby affecting the stability of the continuous marketing process and the relevance of subsequent interactive content. Summary of the Invention

[0005] To address the shortcomings of existing technologies, this invention provides a multi-agent collaborative marketing digital employee interaction method to solve the problems mentioned in the background section.

[0006] To achieve the above objectives, the present invention provides the following technical solution: a multi-agent collaborative marketing digital employee interaction method, comprising: S1. Collect channel interaction records, manual processing records, and business confirmation records of target customers within a preset marketing cycle, sort them according to a unified time base, and generate a continuous marketing conversation ledger. S2. Extract the current marketing stage, current channel status, current responsible entity, confirmed items, prohibited repeated inquiries, and pending items from each session segment in the continuous marketing session ledger to form a current session status record; S3. Based on the current session state record, extract the allowed acceptance stage, allowed acceptance channel, allowed acceptance subject, must-inherit content, must-avoid content, and transition trigger conditions to generate an acceptance constraint record; S4. Retrieve the subject attributes, channel attributes, and task attributes of the marketing digital employee to be executed, and verify them against the acceptance constraint record item by item to generate the current acceptance qualification result; S5. When the current qualification result is valid, marketing interactions are performed based on the mandatory inheritance content, mandatory avoidance content, prohibited repeated inquiry items, and pending items in the acceptance constraint record to generate the current round of interaction results. S6. Extract newly confirmed items, stage change information, and channel status change information from the current round of interaction results and write them back to the continuous marketing session ledger. When the transition trigger conditions are met, regenerate the acceptance constraint record and enter the next round of acceptance qualification verification.

[0007] Furthermore, S1 includes: Filter channel interaction records, manual processing records, and business confirmation records by primary customer number; The selected records are filtered according to the preset marketing cycle; The filtered records are converted to a time based on a unified time standard; Perform lead and trailing space removal, space folding, line break folding, and separator folding on the interactive content records and processing item records; Complete the interaction end time in the channel interaction record; Remove duplicates from the converted records; A continuous marketing session ledger is generated by sorting channel interaction records, manual processing records, and business confirmation records according to the time of occurrence.

[0008] Furthermore, S2 includes: Read the main items, record category, and original record citation number of each session segment in the continuous marketing session ledger according to the time of occurrence; Extract the current marketing stage, current channel status, current responsible entity, confirmed matters, matters that should not be repeatedly inquired about, and matters that need to be promoted; Generate the current session status record based on the primary customer number, the batch number, and the sequence number of the last ledger record read.

[0009] Furthermore, S3 includes: Retrieve the current session state record; Based on the current marketing stage, current channel status, current undertaking entity, confirmed matters, prohibited repeated inquiries, and pending matters, extract the allowed undertaking stage, allowed undertaking channel, allowed undertaking entity, mandatory inherited content, mandatory avoided content, and transition trigger conditions; Generate acceptance constraint records based on the main customer number, collection batch number, and status record number.

[0010] Furthermore, S4 includes: Retrieve the acceptance constraint record; Retrieve the subject attributes, channel attributes, and task attributes of the marketing digital employees to be executed; The subject attributes, channel attributes, and task attributes are checked item by item along with the acceptance constraint records in the order of subject attributes, channel attributes, and task attributes. Generate the current qualification results based on the main customer number, collection batch number, constraint record number, and pending marketing digital employee identifier.

[0011] Furthermore, the current eligibility results include: Result of verification of main attributes, result of verification of channel attributes, result of verification of task attributes, comprehensive undertaking qualification identifier, time of qualification formation, and version number of qualification rules; When the verification results of the main body attribute, channel attribute, and task attribute are all passed, the comprehensive qualification mark indicates that the contractor is qualified to undertake the project. In other generated result scenarios, the comprehensive qualification identifier will be marked as not having the qualification to undertake the task.

[0012] Furthermore, S5 includes: Retrieve the current eligibility results and acceptance constraint records; When the comprehensive qualification mark indicates that the contractor is qualified, the interactive content of this round is formed in the following order: first inheritance, then avoidance, then removal of duplicate inquiries, and finally retention of items to be promoted. The content to be inherited, the content to be avoided, the items to be repeatedly inquired about, and the items to be promoted are all in order. The marketing digital staff to be executed initiates this round of marketing interaction through the channels to be used, and the result of this round of interaction is formed by the formal interaction record.

[0013] Furthermore, S6 includes: Retrieve the interaction results of this round by main customer number, collection batch number, and interaction result number; Extract newly confirmed items, stage change information, and channel status change information; The cost cycle is recorded in the ledger and appended to the continuous marketing conversation ledger, following the order of newly confirmed items, stage change information, and channel status change information. Using the transition trigger conditions already written in the previous valid acceptance constraint record as the basis for judgment, when the transition trigger conditions are met, the acceptance constraint record is regenerated based on the newly formed current session state record, and the new constraint record number is submitted to the acceptance qualification verification execution unit.

[0014] Compared with the prior art, the present invention has the following beneficial effects: 1. By collecting channel interaction records, manual processing records, and business confirmation records of target customers within a preset marketing cycle, a continuous marketing conversation ledger is generated. This ledger further extracts the current marketing stage, current channel status, current responsible entity, confirmed items, prohibited duplicate inquiries, and pending items, forming a responsible constraint record. The eligibility of marketing digital employees to be executed is then verified item by item. When the current eligibility result is valid, marketing interactions are executed based on mandatory inheritance content, mandatory avoidance content, prohibited duplicate inquiries, and pending items. This achieves the effect of ensuring consistent and continuous marketing responsible interfaces between different channels and entities in a multi-agent collaborative marketing scenario, avoiding duplicate inquiries, preventing confirmed items from being repeatedly triggered, and preventing disconnections between different channels and entities.

[0015] 2. By extracting newly confirmed items, stage change information, and channel status change information after each round of marketing interaction and writing them back to the continuous marketing conversation ledger, and then regenerating the acceptance constraint record based on the transition trigger conditions and entering the next round of acceptance qualification verification, the system can achieve the effect of enabling the target customer's stage advancement, channel switching, and subject switching in the continuous marketing service process to be linked in a closed loop around the same ledger and the same acceptance rules, thereby improving the continuous acceptance capability of multiple rounds of marketing interaction and the accuracy of subsequent acceptance actions. Attached Figure Description

[0016] Figure 1 A schematic diagram of the overall process of a multi-agent collaborative marketing digital employee interaction method; Figure 2 A diagram illustrating the collection and generation of a continuous marketing conversation ledger from channel interaction records, manual processing records, and business confirmation records; Figure 3 A diagram illustrating the extraction of the current session state record; Figure 4 A schematic diagram is generated to record the constraints. Figure 5 This is to generate a schematic diagram for qualification verification and this round of marketing interactions; Figure 6 This is a schematic diagram illustrating the write-back of the results of this round of interaction and the triggering of the next round of interaction. Detailed Implementation

[0017] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0018] Example: Combined with Appendix Figures 1-6 This embodiment provides a multi-agent collaborative marketing digital employee interaction method, including: S1. Collect channel interaction records, manual processing records, and business confirmation records of target customers within a preset marketing cycle, sort them according to a unified time base, and generate a continuous marketing conversation ledger. The specific implementation is as follows: The continuous marketing service process surrounding the target customer involves a conversation processing and execution unit located at the enterprise's marketing site. At the start of each batch of data collection, this unit retrieves existing channel interaction records, manual processing records, and business confirmation records for that target customer. These records are then merged and processed within the same target customer, the same marketing task scope, and the same timeframe. The target customer is defined as a single customer entity that is continuously reached within this marketing task. The target customer uses the primary customer number in the enterprise's customer master file as a unique identification field. All primary customer number mappings between different channel accounts are uniformly merged into the same target customer. Accounts that have not been mapped will not be included in this collection. When the same natural person has multiple unmerged primary customer numbers, only the primary customer number specified in the current marketing task will be collected. The preset marketing cycle is limited to the time interval for the collection of records corresponding to this marketing task. Its starting point is the later of the effective time of the marketing task and the time when the last record that can continue to be carried over in the previous collection batch occurred. The ending point is the start time of this collection batch. It will not cross the case closure cycle that has formed a case closure mark and does not allow the addition of records again. The case closure mark is fixed to the case closure status mark written by the marketing task in the task configuration record or business archive record.

[0019] Channel interaction records are taken from the original interaction traces of SMS outreach, outbound call agents, social messaging, and web-based inquiry. All message exchanges, call exchanges, and web-based inquiry exchanges directly involving the target customer are uniformly recorded in the channel interaction record. When collecting these records, at least the main customer number, channel identifier, interaction initiation time, interaction end time, interaction topic, interaction content, and interaction result must be retained. Among these, the interaction topic record prioritizes the topic field submitted by the source system. If the source system does not have an independent topic field, the topic identifier field of the business page where the interaction occurred is used, and it is not automatically extracted from the text. Manual processing records are taken from the manual processing traces of agent handling pages, operations personnel follow-up pages, and pre-sales consultant registration pages. All handling actions, remarks, and follow-up actions completed by internal personnel on internal pages are uniformly recorded in the manual processing record. When compiling records, at least the primary customer number, the handler's identifier, the time of processing, the details of the processing, and the processing conclusion should be retained. Browsing traces that only exist but do not result in a submission are not included in the manual processing records. Business confirmation records are taken from the formal confirmation traces on the order confirmation page, event registration confirmation page, rights confirmation page, and appointment confirmation page. Any action that results in a formal change to the customer's rights, appointment, registration, order, or plan confirmation status and is written to the business confirmation page is uniformly recorded in the business confirmation record. When compiling, at least the primary customer number, confirmation item name, confirmation completion time, and confirmation result should be retained. Confirmation items that are in draft, withdrawn, or beyond the scope of the current marketing task are not included in the business confirmation record. If the same item involves both external interaction and internal processing, they should be compiled independently according to their respective categories and should not be substituted for each other.

[0020] During data collection, the original data is first retrieved according to the record source. Then, a first screening is performed by the main customer number, retaining only records consistent with the target customer. Subsequently, a second screening is performed according to the preset marketing cycle, retaining only records whose occurrence time falls within that time interval. Time conversion is then performed according to a unified time base, which is fixed as Beijing time second-level timestamp. The time offset is determined according to the time mapping table corresponding to the record source system. The time mapping table is fixed to the time difference mapping table preset for each source system in the unified time configuration record of the enterprise marketing business site. If the source system does not have a valid time offset, the record is transferred to the pending verification area and is not included in the unified sorting. For records of interactive content and processing matters, only the first and last spaces are removed, two or more consecutive spaces are folded into one space, two or more consecutive line breaks are folded into one line break, and two or more consecutive separators are folded into one separator. Chinese characters, numbers, and punctuation marks in the text are not deleted, and the sentence order is not rewritten. The original full text is retained separately according to the original record citation number.

[0021] For missing fields, only the interaction end time in the channel interaction record is allowed to be filled in, provided that the closed status field in the source system is valid and there is a closed submission time. When filling in the missing field, the closed submission time is written into the interaction end time, and the missing field is written in simultaneously to form a mark. If the closed status field is valid but the closed submission time is missing, it is moved to the pending record area. The main customer number, interaction initiation time, processing conclusion record, and confirmation result record cannot be automatically filled in. If the above fields are missing, the record will stop being processed.

[0022] For duplicate records, if the source serial number is valid, it is used as the unique deduplication primary key. If the source serial number is missing, the main customer number, record category, occurrence time, and main items recorded after noise removal are completely consistent as the alternative judgment condition. Among them, the main items are recorded in channel interaction records by concatenating the interaction topic first and the interaction result second. In manual processing records, the processing item is recorded first. In business confirmation records, the confirmation item name is concatenated first and the confirmation result is recorded second.

[0023] After filtering, time conversion, noise reduction, completion, and deduplication, channel interaction records, manual processing records, and business confirmation records are mixed and sorted from earliest to latest according to a unified time base. The sorting primary key is fixed as the occurrence time. When the occurrence times are the same, the priority order is fixed as channel interaction records, manual processing records, and business confirmation records. If they are still the same, they are arranged in ascending order by source serial number. If the source serial number is empty or the same, they are arranged in ascending order by the original record entry time. The original record entry time is fixed as the completion time when the source system writes the record into the source record database. If the original record entry times are still the same, they are arranged in ascending order by the record retrieval sequence number. The record retrieval sequence number is fixed as the consecutive sequential number generated when the source records are retrieved in this collection batch.

[0024] After sorting, a continuous marketing conversation ledger is generated. Only one valid continuous marketing conversation ledger is retained for the same target customer within the same marketing task scope and the same preset marketing cycle. New collection batches are only allowed to add records to this ledger and no parallel valid ledgers are generated. Each ledger record must include at least the main customer number, record category, source system identifier, occurrence time, main event record, original record reference number, and collection batch number. Before submission, the collection rule version number, time base version number, and source mapping version number are written synchronously. The aforementioned versions are all read and written to the current batch when the collection batch starts. Subsequent version updates cannot retroactively overwrite batches that have already been entered. Before recording interaction content, processing event records, and confirmation event names, a fixed mask is applied to the middle 4 digits of the mobile phone number, the middle 8 digits of the ID number, and the detailed address number. Original records involving payment passwords, complete ID images, and biometric content are not included in the main text area of ​​the continuous marketing conversation ledger; only the original record reference number is retained.

[0025] When writing to the continuous marketing session ledger, if the same collection batch number is submitted again, only unsuccessfully entered records are allowed to be added; successfully entered records are not added again. After writing is completed, the main customer number, collection batch number, ledger record number, record category, occurrence time, and main event record are submitted to the next stage. Successful submission is based on the return of a write confirmation flag from the ledger storage area. If a write confirmation flag is not obtained, the current batch is only resubmitted a certain number of times at a fixed interval determined by the preset submission parameters corresponding to the collection rule version number. The fixed interval and the number of resubmissions are locked when the collection batch is started and will not be changed within the current batch. If the resubmission is still unsuccessful, the current batch is transferred to the waiting area for supplementation, while the previous valid batch remains accessible.

[0026] S2. Extract the current marketing stage, current channel status, current responsible entity, confirmed items, prohibited duplicate inquiries, and pending items from each session segment in the continuous marketing session ledger to form a current session status record. The specific implementation is as follows: After the current batch of data collection is written to the continuous marketing conversation ledger, the conversation status processing and execution unit set up at the enterprise's marketing business site retrieves the continuous marketing conversation ledger records corresponding to the batch by the main customer number. It then sequentially extracts the status of each entered conversation segment only within the same target customer, the same marketing task scope, and the same preset marketing cycle. The conversation segment is fixed as the smallest extraction unit corresponding to a single ledger record in the continuous marketing conversation ledger. One ledger record corresponds to only one conversation segment. In this step, the conversation segment is not split again by item, not spliced ​​across ledger records, and not merged across target customers. The reading cutoff time is fixed as the occurrence time of the last conversation segment involved in the extraction, and the reading cutoff ledger record sequence number is fixed as the ledger record sequence number corresponding to the last conversation segment involved in the extraction.

[0027] When extracting the current marketing stage, first, read the main items, record categories, and original record citation numbers of each conversation segment from morning to evening according to the time of occurrence. Then, compare each item with the stage division criteria that have been activated in the task configuration page and locked at the start of this extraction. The current marketing stage is fixed to the latest valid stage identifier corresponding to the target customer at the end of the extraction. The stage division criteria include at least 6 categories: initial contact, interest establishment, solution communication, appointment confirmation, sales conversion, and service follow-up. Among them, if there is only a record of the first round of contact without a clear response from the customer, it is recorded as initial contact; if there are records of the customer taking the initiative to reply, inquire, or express interest, it is recorded as interest establishment; if there are records of price, benefits, solution explanation, or condition confirmation, it is recorded as solution communication; if there are records of appointment time, in-store arrangement, or service schedule confirmation, it is recorded as appointment confirmation; if there are records of order confirmation, it is recorded as order confirmation. Records of confirmation, payment completion, and contract signing completion are recorded as transaction conversions. Records of performance reminders, after-sales follow-ups, and service follow-ups are recorded as service follow-ups. If each conversation segment has a clear stage identifier in the original record reference number corresponding to the original trace, the stage identifier is directly extracted. If there is no clear stage identifier, the stage identifier is determined item by item according to the names of the items already recorded in the main items and the aforementioned stage division criteria. If the same conversation segment meets multiple stage conditions at the same time, the stage with the later order is always used as the stage result of the conversation segment. If no stage conditions are met, the stage result already determined in the previous conversation segment is maintained. If the first conversation segment has no previous stage result and does not meet any stage conditions, it is always recorded as the initial contact. Within the same continuous marketing conversation ledger, the current marketing stage can only remain unchanged or be updated to a stage with a later order. Rollback is not allowed without a clear rollback record.

[0028] When extracting the current channel status, the source system status value corresponding to the record category and original record reference number of each session fragment is used as the source. The current channel status permanently represents the actual reception status of the target customer on the corresponding channel at the time of retrieval, including at least five types of status: pending response, responded, ongoing communication, manual connection, and closed. Among them, if the enterprise has formed a contact record, the target customer has not yet formed a reply record, and the closed status field of the source system is not effective, it is recorded as pending response; if the target customer has formed an initial reply record but no subsequent continuous round-trip communication has occurred, it is recorded as responded; if at least one customer reply has occurred and at least one follow-up reply has occurred under the same channel, it is recorded as ongoing communication; if the manual connection indicator is valid in the source record and the subsequent reception entity is switched to a human agent or operations personnel, it is recorded as manual connection. If the closed status field is valid or the business confirmation record indicates that the corresponding item for the current channel has been closed, it is recorded as closed. Channel interaction records take priority to use the original status value of the source system. If the original status value is not within the aforementioned 5 status categories, it is converted and written according to the status mapping caliber locked at the beginning of this extraction. The status mapping caliber is fixed to the channel status mapping table where the current marketing task has taken effect. One source system status value is only allowed to be mapped to one current channel status. If the manual processing record contains a manual continuation conclusion, it is directly recorded as manual continuation. If the business confirmation record contains confirmation of completion and the corresponding current channel has been closed, it is directly recorded as closed. When there are multiple channel status sources at the same time, they are determined in the order of business confirmation record, manual processing record, and channel interaction record. If they are not at the same time, the result of the conversation segment with the later time is used to determine the status.

[0029] When extracting the current receiving entity, each conversation segment is grouped according to its original record citation number, including the initiator identifier, processing personnel identifier, and confirmation / submission personnel identifier. The current receiving entity is fixed as the entity responsible for continuing communication with the target customer at the end of the reading period. Entity identifiers are fixedly categorized into three types: marketing digital employees, human agents, and operations personnel. Entities automatically reached via SMS, outbound calls, and social media messages are uniformly classified as marketing digital employees; real-time conversation receivers and pre-sales consultants are uniformly classified as human agents; and back-end registration personnel, order follow-up personnel, and review personnel are uniformly classified as operations personnel. Channel interaction records... If the initiator's identifier corresponds to the automatically reached entity, it is recorded as the corresponding marketing digital employee. If the handler's identifier in the manual processing record is valid, it is recorded as the corresponding human agent or operations personnel. The business confirmation record only retains the entity result of the previous session segment if no new handler's identifier appears and the entity result of the previous session segment is valid. If it indicates acceptance of changes, it is updated according to the confirmed submission personnel identifier. If no valid entity identifier is obtained for the same session segment, no entity is automatically created. The current accepting entity already determined in the previous session segment is retained. If the first session segment has no preceding entity result and no valid entity identifier is obtained, this extraction is stopped and transferred to the pending verification area.

[0030] When retrieving confirmed items, the search is performed in the following order: business confirmation records in each conversation segment, manual processing records indicating confirmation conclusions, and channel interaction records indicating clear customer responses. Confirmed items are fixed as a set of items that have formed clear confirmation results and are still in a valid state at the time of the read deadline. The item names are uniformly adopted as the item names after merging the item definition table of the current marketing task. Only one set of item definition table is called for the same marketing task within the same validity period. Different descriptions in the original traces but pointing to the same business item are merged into one item. The valid state is fixed as the item not having any withdrawal, cancellation, or invalidation records before the read deadline and not exceeding the scope of the current marketing task. If the same item is confirmed multiple times, only the one with the latest occurrence time and a valid state is retained.

[0031] When extracting items that should not be asked repeatedly, each item is checked according to whether it has been explicitly asked in each conversation segment and subsequently received a valid response, whether it has been confirmed in business, or whether it has been registered in the manual processing record as items that should not be asked again. Items that should not be asked repeatedly to the target customer at the deadline for reading are included in items that should not be included in items that should not be asked repeatedly. Items that have been explicitly rejected by the customer and have resulted in a valid rejection conclusion are included in items that should not be asked repeatedly. They are not included in confirmed items or items that are pending. Only one valid item should be marked as not to be asked repeatedly.

[0032] When extracting items to be promoted, each item in each conversation segment that has not yet been confirmed, has not yet been closed, and has been merged according to the item category table is filtered out one by one. Items to be promoted are fixed as the set of items that still need to be taken on and completed at the deadline for reading. Among them, items that customers have put forward but have not been confirmed, follow-up items registered in the manual processing record, and items that have entered the formal confirmation process in the business confirmation record but whose confirmation result has not yet been written as completed and are not in the draft or withdrawn state can all be included in items to be promoted. If the same item is included in the confirmed items, or is recorded as canceled, invalid, or closed, it will be removed from the items to be promoted. Items to be promoted cannot coexist with confirmed items.

[0033] After completing the above extraction, generate a current session status record based on the main customer number, collection batch number, and read-off ledger record sequence number. The current session status record must include at least the main customer number, collection batch number, current marketing stage, current channel status, current receiving entity, confirmed items, prohibited duplicate inquiries, pending items, status formation time, and status rule version number. The status formation time is fixed to the occurrence time of the last session segment involved in the extraction. The status rule version number is read and locked at the beginning of this extraction. The current session status record that has already been written will not be overwritten by subsequent rule version retrospectives. Only one valid current session status record is retained under the same main customer number, the same collection batch number, and the same read-off ledger record sequence number. Records that were not written in the previous extraction are allowed to be overwritten. Records that were written in the previous extraction will not be duplicated in this extraction.

[0034] After the current session status record is generated, it is written into the session status record storage area in the order of main customer number, collection batch number, and read end-of-ledger record sequence number. Then, the main customer number, collection batch number, status record number, current marketing stage, current channel status, and current undertaking entity are submitted to the next stage for direct access to subsequent undertaking constraints.

[0035] S3. Based on the current session state record, extract the allowed transition stage, allowed transition channel, allowed transition subject, required inherited content, required avoided content, and transition trigger conditions to generate a transition constraint record. The specific implementation is as follows: After the current session status record is written, the acceptance constraint processing and execution unit, located at the enterprise marketing business site, retrieves the corresponding current session status record by main customer number, collection batch number, and status record number. Within the same target customer, the same marketing task scope, and the same preset marketing cycle, it extracts the allowed acceptance stage, allowed acceptance channel, allowed acceptance entity, required inheritance content, required avoidance content, and transition trigger conditions in sequence based on the current marketing stage, current channel status, current acceptance entity, confirmed matters, prohibited repeated inquiries, and pending matters, generating acceptance constraint records. The acceptance constraint processing and execution unit is fixed in the session acceptance control link of the marketing business system, and the call time is limited to the valid acceptance window where the current session status record has been formed and has not expired. The current session status record uses the formal status record written to the session status record storage area in the previous step, and does not call draft records, historical expired records, or cross-marketing task records.

[0036] The acceptance rule table used for extraction is fixed to the acceptance rule table that has been configured and taken effect before the start of the current marketing task. The acceptance rule table is uniquely bound to the current marketing task identifier. Only one set of acceptance rule table is called within the validity period of the same marketing task. The acceptance rule table includes at least the stage scope field, channel scope field, subject scope field, inherited content field, avoidance content field, transition condition field, priority order field, and version number field. It is locked at the start of this extraction and will not be changed by subsequent background adjustments.

[0037] When extracting the allowed transition stages, first read the current marketing stage, confirmed items, and pending items from the current session state record, then compare each item with the transition path table. The allowed transition stages are fixed as a set of discrete stages. When the mandatory items corresponding to the current marketing stage have not yet been fully closed and the mandatory items for that stage are still retained in the pending items, the allowed transition stage only retains the current marketing stage. When all the mandatory items corresponding to the current marketing stage have entered the confirmed items, and the transition path table indicates that it can enter the subsequent stage, the allowed transition stage is expanded to the current marketing stage and the immediately following stage. Among them, the mandatory items for the stage are fixedly the items marked as necessary for the completion of the stage in the transition path table corresponding to the current marketing stage. Stage closure is fixedly defined as all the aforementioned mandatory items for the stage entering the confirmed items and no longer existing in the pending items. If the transition path table indicates that the current stage cannot be rolled back after closure, the allowed transition stage does not include the stage with the highest priority. If the same state record meets multiple stage extension conditions at the same time, only the current marketing stage and the nearest subsequent stage are fixedly retained, and the transition is not directly opened without crossing intermediate stages.

[0038] When extracting allowed channels, the current channel status, prohibited duplicate inquiries, and pending items in the current session status record are read. These are then screened item by item against the channel scope field corresponding to the current marketing stage in the channel acceptance table. Allowed channels are fixed as a set of channels. Among these, currently contacted channels are those belonging to the most recent valid session segment that formed the current channel status. For channels with current statuses of pending response, responded, or ongoing communication, allowed channels are prioritized for retention. If the channel acceptance table specifies other channels that can be opened in parallel, then those other channels are included. If the channel acceptance table does not specify a maximum number of parallel channels, all specified channels are used. Other channels are included in the permitted channels; for channels currently in the manual connection stage, the permitted channels are only those corresponding to the manual connection and those listed in the interface table as being accessible only to manual entities; for channels currently in the closed stage, the permitted channels will no longer retain closed channels, and will only be included as transferable channels if there are unclosed items in the pending items and the interface table indicates that transfer is permitted, and will not be transferred back to the original closed channel; for items that are prohibited from repeated inquiries, the corresponding channel will be fixed to the channel identifier where the item first formed a valid response or first formed a valid prohibited repeated mark, and the corresponding channel marked as prohibited from being triggered again will not be included in the permitted channels.

[0039] When extracting allowed recipient entities, the current recipient entity, current marketing stage, and current channel status are read from the current session state record. These are then merged item by item according to the stage entity correspondence and channel entity correspondence in the recipient interface table. Allowed recipient entities are fixed as a set of entities that can be received, not the same as the final execution entity. Specifically, the stage entity correspondence refers to the pre-written entity correspondence in the recipient interface table for each current marketing stage, and the channel entity correspondence refers to the pre-written entity correspondence in the recipient interface table for each allowed channel. The current recipient entity is the marketing digital staff. If the current channel status has not yet entered the manual handling phase, the undertaking entity is allowed to retain marketing digital staff first. If the undertaking interface table indicates that manual intervention is possible, then human agents will be added. If the current undertaking entity is a human agent, the undertaking entity is allowed to retain human agents. If the undertaking interface table indicates that the back-end order follow-up can continue to undertake the task, then operations personnel will be added. If the current undertaking entity is operations personnel and the current channel status has been closed, marketing digital staff will not be allowed to take on the task again. If the same status record meets the conditions for opening multiple entities, only the entity that is listed in both the current allowed undertaking stage field and the current allowed undertaking channel field will be retained.

[0040] When extracting mandatory inherited content, read the confirmed items, current marketing stage, and current undertaking entity from the current session status record, and organize them according to the inherited content field order in the undertaking interface table. Mandatory inherited content is fixedly expressed as a set of item names, which is a set of content that must be continuously referenced in subsequent undertakings and whose existing result scope cannot be changed. Among them, all valid items in the confirmed items are included, the stage identifier corresponding to the current marketing stage is included, the commitment items formed by the current undertaking entity and not revoked, the condition items that have been clearly explained to the target customer and have not been changed subsequently, and the registration items that have been written into the business confirmation record or manual processing record and whose status is validly completed are included in the mandatory inherited content if the undertaking interface table indicates that they need to be continuously maintained. If the same content appears repeatedly in multiple sources, only the one item with the latest occurrence time and valid status is retained. If a new record of the same inherited content appears later but no undertaking change identifier is formed, the previous valid content shall still be used.

[0041] When extracting content that must be avoided, the system reads the prohibited repeated inquiry items, current channel status, and confirmed items from the current session status record, and determines each item according to the avoidance content field in the acceptance interface table. The content that must be avoided is fixed and expressed as a set of item names, which is a set of items that cannot be initiated, confirmed, or triggered by marketing again in subsequent acceptance. Among them, all prohibited repeated inquiry items are included, items in the acceptance interface table that are specified as not to be inquired again after confirmation are included, closed-loop items of the corresponding channel whose current channel status has been closed are included, and items that the customer has explicitly refused and a valid refusal conclusion has been formed are retained in the content that must be avoided and are not included in the content that must be inherited. The same item can be included in both the content that must be inherited and the content that must be avoided at the same time. Entering the content that must be inherited means that the existing result must be used in subsequent acceptance, while entering the content that must be avoided means that the item cannot be inquired or confirmed again in subsequent acceptance.

[0042] When extracting transition trigger conditions, the current marketing stage, confirmed items, pending items, and current channel status are read from the current session status record. Each item in the transition condition field of the interface path table is matched against these conditions. The transition trigger conditions are a fixed set of conditions that must be met simultaneously for the current marketing stage to transition to the next stage. Specifically, items marked as necessary for the completion of the current marketing stage in the interface path table are recorded as confirmed items, which are considered core item confirmed conditions. The current channel status matching condition is recorded when the current channel status reaches the target channel status listed in the interface path table for transitioning from the current marketing stage to the next stage. The condition for clearing pending items in the current stage is recorded when any of the mandatory items for the current stage are no longer present in the pending items. These three types of conditions must be met simultaneously; the transition trigger condition is considered valid only when all three are met. The failure to clear non-mandatory items for the current stage does not affect the validity of the current stage's transition trigger conditions.

[0043] After completing the above extraction, a binding constraint record is generated based on the main customer number, collection batch number, and status record number. The binding constraint record must include at least the main customer number, collection batch number, status record number, allowed binding stage, allowed binding channel, allowed binding entity, required inherited content, required avoided content, prohibited repeated inquiry items, pending progress items, transition trigger condition, constraint formation time, and binding interface version number. The constraint formation time is fixed to the completion time of writing this binding constraint record. The binding interface version number is read and locked at the beginning of this extraction. The binding constraint record that has already been written will not be overwritten due to subsequent binding interface adjustments. Only one valid binding constraint record is retained under the same main customer number, collection batch number, and status record number. Records that were not written in the previous extraction are allowed to be overwritten. Records that were written in the previous extraction and whose binding interface version number has not changed will not be regenerated in this extraction.

[0044] After the acceptance constraint record is generated, it is written into the acceptance constraint record storage area in the order of main customer number, collection batch number, and status record number. Then, the main customer number, collection batch number, constraint record number, allowed acceptance stage, allowed acceptance channel, and allowed acceptance entity are submitted to the next stage. The next stage retrieves the required inheritance content, required avoidance content, prohibited repeated inquiry items, pending progress items, and transition trigger conditions from the acceptance constraint record storage area based on the constraint record number.

[0045] S4. Retrieve the subject attributes, channel attributes, and task attributes of the marketing digital employee to be executed, and verify them item by item against the acceptance constraint record to generate the current acceptance qualification result. The specific implementation is as follows: After the acceptance constraint record is written, the acceptance qualification verification execution unit set up at the enterprise marketing business site retrieves the corresponding acceptance constraint record according to the main customer number, collection batch number, and constraint record number. Within the same target customer, the same marketing task scope, and the same preset marketing cycle, it retrieves the subject attributes, channel attributes, and task attributes of the marketing digital employees to be executed from the queue to be executed. Then, it verifies the aforementioned subject attributes, channel attributes, and task attributes against the acceptance constraint record item by item to generate the current acceptance qualification result. Among them, the queue to be executed is fixed to the candidate sequence of marketing digital employees who have completed the queue registration under the current marketing task but have not yet actually initiated this round of marketing interaction. The marketing digital employees to be executed are fixed to the automatic acceptance subjects in the aforementioned candidate sequence that have been selected to enter this verification but have not yet executed this round of interaction.

[0046] The subject attributes are fixed and use the subject category, scope of available stages, scope of available channels, scope of available tasks, manual connection restriction flag, and deactivation flag that the marketing digital employee to be executed is already effective in the subject file and locked at the start of this verification. The subject category is at least subdivided into SMS automatic contact subject category, outbound call automatic contact subject category, and social message automatic contact subject category. The aforementioned subject categories are uniformly classified under the marketing digital employee category. The scope of available stages, scope of available channels, and scope of available tasks are all fixed and expressed using discrete sets. The manual connection restriction flag is fixed and indicates whether the marketing digital employee to be executed is still allowed to continue to automatically initiate communication after the manual subject has been connected. It includes at least two values: allow to continue to automatically accept, and prohibit to continue to automatically accept.

[0047] The channel attributes are fixed and are the channel identifier, channel open status, channel compatible subject category, channel available stage range, and channel trigger restriction identifier that have been effective in the channel file and locked at the start of this verification. The channel to be used is the target channel that has been pre-specified by the current marketing task for the marketing digital employee to be executed and has not yet been actually triggered. The channel open status includes at least three types: open, closed, and paused. Only the open status is considered effective.

[0048] The task attributes are fixed and use the task identifier, task stage range, task channel range, task item range, prohibited trigger items, and task transition restriction identifier corresponding to the marketing task to be executed. Among them, the executable task range is fixed to the set of marketing task items that are allowed to be initiated by the marketing digital employee to be executed in the main file, and the task item range is fixed to the set of items that are allowed to be executed in the current marketing task.

[0049] When retrieving subject attributes, first locate the corresponding subject configuration in the subject file according to the marketing digital employee ID to be executed, then filter the currently valid records according to the effective period of the subject configuration, and only retain the subject attributes that are consistent with the time of this verification. If the subject file has a deactivated mark that is valid, stop the subsequent verification and transfer it to the pending verification area. The pending verification area shall retain at least the main customer number, collection batch number, constraint record number, marketing digital employee ID to be executed, and the reason for stopping, and shall not generate the current undertaking qualification result.

[0050] When retrieving channel attributes, first locate the corresponding channel configuration in the channel file according to the channel identifier to be used, and then screen the current valid channel attributes according to the channel open status and task adaptation scope. If the channel open status is not open, stop the subsequent verification and generate the current qualification result. The comprehensive qualification identifier is recorded as not having the qualification to undertake. Verification items that are not continued to be executed are uniformly recorded as failing.

[0051] When retrieving task attributes, locate the corresponding task configuration in the task configuration record according to the task identifier, and then filter the currently valid task attributes according to the task validity period. If the task configuration is invalid, stop the subsequent verification and transfer it to the pending verification area, and do not generate the current qualification result.

[0052] After completing the above retrieval, the subject attributes are checked against the acceptance constraint records item by item. The subject category, acceptable stage range, and acceptable channel range in the subject attributes are compared in the following order: subject category, acceptable stage range, acceptable channel range, and manual connection restriction identifier. If the subject category is not listed as an allowed subject, the subject attribute check result is directly determined to be unsuccessful. If the subject category is listed as an allowed subject but the acceptable stage range does not cover the allowed stage, the subject attribute check result is determined to be unsuccessful. If the acceptable stage range covers the allowed stage but the acceptable channel range does not cover the allowed channel, the subject attribute check result is determined to be unsuccessful. If all the above comparisons pass, but the manual connection restriction identifier prohibits continued automatic acceptance and the acceptance constraint record states that only manual subjects can continue to accept in the current channel, the subject attribute check result is determined to be unsuccessful. If all of the above conditions are met, the subject attribute check result is determined to be successful.

[0053] When verifying channel attributes against acceptance constraint records item by item, the comparison is performed in the following order: channel identifier, channel matching entity category, channel acceptance stage range, and channel trigger restriction identifier. If the channel identifier is not listed as a permitted channel, the channel attribute verification result is deemed unsuccessful. If the channel identifier is permitted but the channel matching entity category does not include the entity category corresponding to the marketing digital employee to be executed, the channel attribute verification result is deemed unsuccessful. If the channel matching entity category includes the entity category but the channel acceptance stage range does not cover the permitted acceptance stage, the channel attribute verification result is deemed unsuccessful. If all the above comparisons pass, but the channel trigger restriction identifier overlaps with the content that must be avoided, the channel attribute verification result is deemed unsuccessful. The aforementioned overlap specifically refers to the proposed channel being marked as prohibited from reaching a certain matter in the channel file, and that matter also appears in the content that must be avoided. If all of the above conditions are met, the channel attribute verification result is deemed successful.

[0054] When verifying task attributes against acceptance constraint records item by item, the comparison is performed sequentially in the order of task stage scope, task channel scope, task item scope, and task transition restriction identifier. If the task stage scope does not cover the allowed acceptance stage, the task attribute verification result is deemed unsuccessful; if the task stage scope covers the allowed acceptance stage but the task channel scope does not cover the allowed acceptance channel, the task attribute verification result is deemed unsuccessful. After all the above comparisons pass, the task item scope is then compared with the item name category content in the mandatory inheritance content. At the same time, the inheritance retention fields in the task stage scope and task configuration are compared with the stage identifier, commitment item, condition item, and registration item in the mandatory inheritance content. The inheritance retention fields are fixed to the stage identifier and commitment item used in the task configuration record to mark the stage that must be continuously used. If the task's scope does not cover the item name category of the mandatory inheritance content, or if the inheritance retention field in the task configuration does not cover the stage identifier, commitment item, condition item, or registration item of the mandatory inheritance content, the task attribute verification result is deemed unsuccessful. If the task's scope includes items corresponding to mandatory avoidance content, the task attribute verification result is directly deemed unsuccessful. If there is overlap between prohibited triggering items and mandatory avoidance content, it is recorded as consistent avoidance and is not treated as a conflict. If all the above comparisons pass, but the task transition restriction identifier prohibits the current stage from continuing to undertake or prohibits entering the allowed stage where the undertaking constraint record has been released, the task attribute verification result is deemed unsuccessful. If all of the above conditions are met, the task attribute verification result is deemed successful.

[0055] The order of item-by-item verification is fixed as main attribute, channel attribute, and task attribute. Any verification item that is not executed due to the cessation of subsequent verification is recorded as failing. If the previous verification fails, the next verification is still performed and the results of each item are recorded separately. If there are multiple failure points within the same item, only the item with the first conflict according to the comparison order listed in this step is retained as the verification result of that item, and the same type of conflict is not accumulated repeatedly.

[0056] After all verifications are completed, the current qualification result is generated. This result must include at least the main customer number, collection batch number, constraint record number, pending marketing digital employee ID, qualification result number, subject attribute verification result, channel attribute verification result, task attribute verification result, comprehensive qualification identifier, qualification formation time, and qualification rule version number. The qualification result number is a unique number formed by combining the main customer number, collection batch number, constraint record number, pending marketing digital employee ID, and the verification sequence number. The subject attribute verification result, channel attribute verification result, and task attribute verification result are recorded as either "pass" or "fail," respectively. The comprehensive qualification identifier is only used when all three verification results (subject attribute, channel attribute, and task attribute) are "pass," indicating qualification. All other generated results are recorded as not qualified to undertake the task. If the result is transferred to the pending verification area but no current qualification result is generated, it will not be written into the comprehensive qualification identifier. The qualification formation time is fixed to the completion time of this verification. The qualification rule version number is fixed to the qualification verification rule version that corresponds to the main file version number, channel file version number, task configuration version number and undertaking interface version number at the time of this verification. It is locked at the beginning of this verification. The current qualification result that has been written will not be retroactively overwritten due to subsequent file and configuration record adjustments. Only one valid current qualification result is retained under the same main customer number, the same collection batch number, the same constraint record number and the same pending marketing digital employee identifier. If the writing was not completed in the previous time, it is allowed to be overwritten. If the writing was completed in the previous time and the qualification rule version number has not changed, it will not be regenerated in this time.

[0057] Once the current qualification results are generated, they are written into the qualification result storage area in the order of main customer number, collection batch number, constraint record number, and pending marketing digital employee identifier, and then submitted to the next stage with the main customer number, collection batch number, qualification result number, and comprehensive qualification identifier.

[0058] Preferably, within the preset marketing cycle of the most recent 7 days, for one acceptance constraint record, three marketing digital employees awaiting execution can be checked sequentially to form three current acceptance qualification results, of which two are qualified and one is not. Alternatively, without changing the order and scope of retrieving the subject attribute, channel attribute, and task attribute and checking them item by item with the acceptance constraint record to generate the current acceptance qualification result, the marketing digital employees awaiting execution can also be implemented separately for the subject automatically reached by SMS, the subject automatically reached by outbound calls, or the subject automatically reached by social messages.

[0059] S5. When the current acceptance qualification result is valid, marketing interactions are performed based on the mandatory inheritance content, mandatory avoidance content, prohibited duplicate inquiry items, and pending progress items in the acceptance constraint record, generating the current round of interaction results. The specific implementation is as follows: After the current qualification result has been written into the qualification result storage area and the comprehensive qualification identifier is recorded as qualified, the marketing interaction execution unit set up at the enterprise's marketing business site retrieves the corresponding current qualification result by main customer number, collection batch number, and qualification result number, and simultaneously retrieves the corresponding qualification constraint record by constraint record number. Within the same target customer, the same marketing task scope, and the same preset marketing cycle, the marketing digital employee to be executed corresponding to the qualification result initiates this round of marketing interaction through the channel to be used. Among them, the marketing interaction execution unit is fixed as a unified execution unit that schedules and records the actions of the marketing digital employee to be executed. The marketing digital employee to be executed is written into the interaction result as the execution subject identifier, and the channel to be used is fixed as the channel identifier corresponding to the current qualification result verification.

[0060] The current qualification result is valid, which means that the result has been written, the comprehensive qualification identifier indicates that the qualification is available, the qualification rule version number in the qualification result corresponds to the qualification interface table version number and the qualification interface version number in the current qualification constraint record is consistent, and the qualification result has not been replaced by a current qualification result with a later qualification formation time and has been written under the same main customer number, the same collection batch number, the same constraint record number, and the same pending marketing digital employee identifier. If the above conditions are not met, the current marketing interaction will be stopped and the process will be transferred to the verification area. The verification area will at least retain the main customer number, collection batch number, qualification result number, and reason for stopping, and will not generate a result for this round of interaction.

[0061] When executing a marketing interaction, first read the mandatory inherited content from the constraint record. This mandatory inherited content is a fixed set of item names that must be continuously maintained throughout this round of marketing interaction and whose existing outcome cannot be changed. After reading, check the origin of each item in the original record reference number from earliest to latest according to the time of occurrence. Only retain the content that is valid and has not been withdrawn, canceled, or invalidated, and write it into the inheritance context. The inheritance context is a fixed set of content written into the marketing interaction execution unit before this round of marketing interaction, for direct reference in this round of interaction, and is not used as a replacement for independent business records. In this round of interaction, the existing conclusions corresponding to confirmed matters, the stage identifiers corresponding to the current marketing stage, the conditions that have been explained to the target customers and are still valid, and the registration matters that have been registered and are still valid, will all be maintained according to the original recording scope of the inheritance constraint record, and will not be rewritten into new matter names or new confirmation conclusions in this step; if there are multiple valid records for the same content, only the one with the latest occurrence time will be retained as the content to be continued in this round of interaction; if there are multiple valid inherited content sources at the same occurrence time, the business confirmation record will be used first, followed by the manual processing record, and finally the channel interaction record.

[0062] Continue reading the mandatory avoidable content from the constraint record. The mandatory avoidable content is a fixed set of item names that cannot be initiated, confirmed, or reached out to again in this round of marketing interaction. After reading, compare each item name with the items to be initiated in this round. Any item to be initiated that falls into the mandatory avoidable content is directly removed from the items to be initiated in this round and does not enter the interaction content in this round. The control boundary of the mandatory avoidable content is fixed as prohibiting the corresponding item from being re-initiated as an item to be confirmed, an item to be inquired about, or an item to be triggered. It does not prohibit it from being referenced as an existing result in the mandatory inherited content. Items that have been transferred from confirmed items to mandatory avoidable content in the constraint record are allowed to be referenced as existing results in this round of interaction, but are not allowed to ask the target customer for confirmation again. Items that the customer has clearly refused and a valid refusal conclusion has been formed are only retained as mandatory avoidable content and will not enter the items to be initiated in this round.

[0063] Continue reading the prohibited duplicate inquiry items and pending items from the acceptance constraint record. The prohibited duplicate inquiry items and pending items are both component fields of the acceptance constraint record, written to the acceptance constraint record storage area along with the constraint record and retrieved synchronously with the constraint record number. The prohibited duplicate inquiry items are fixed as the set of item names that have been clearly asked and effectively answered in the previous session, and therefore cannot be asked again in this round of marketing interaction. The marketing interaction execution unit compares each item name with the inquiry items to be organized in this round. Any item that has been included in the prohibited duplicate inquiry items will no longer be organized as inquiry-type interaction content, and will be subject to the full-channel prohibition of duplicate questioning control in this round of marketing interaction, which will not be lifted due to changes in the intended channel. If the same item appears in both the mandatory avoidable content and the prohibited duplicate inquiry items, the mandatory avoidable content control shall prevail, and it will not be included in the pending items in this round.

[0064] The "pending progress" items are a fixed set of item names that still need to be completed by the deadline and have not yet entered the confirmed items or closed-loop completion stages. The marketing interaction execution unit checks the relationship between the pending progress items and the mandatory inheritance content, mandatory avoidance content, and prohibited duplicate inquiry items one by one according to the order recorded in the acceptance constraint record. Any pending progress items that fall under the mandatory avoidance content will not enter the current round of interaction execution. Any pending progress items that do not fall under the mandatory avoidance content and the prohibited duplicate inquiry items will all be retained as actual progress items in the current round according to the order recorded in the acceptance constraint record. Among them, when the pending progress items overlap with the mandatory inheritance content, the existing results in the mandatory inheritance content will be used as the premise for progress, and will not be reverted to pending confirmation items. When the pending progress items are items raised by customers but have not yet been confirmed, they will remain progress targets in the current round of interaction. When the pending progress items are items that have entered the formal confirmation process but have not yet been completed, they will remain as continued acceptance items in the current round of interaction, and will not be reverted to initial inquiry items.

[0065] After completing the aforementioned sorting, the marketing interaction execution unit forms the interaction content for this round and initiates the marketing interaction in the order of "inheritance first, avoidance then removal of duplicate inquiries, and finally retention for further progress". The aforementioned order remains fixed under the same qualification result and does not change due to channel differences. The interaction content for this round is fixed as the set of matters actually issued in this round of marketing interaction and their corresponding expression content, excluding content that is only written into the context but not actually initiated.

[0066] After a marketing interaction is initiated, the official interaction record returned by the intended channel serves as the source of the interaction result for this round. The official interaction record is fixed to the interaction record where the intended channel has completed the acceptance of this round of interaction and generated a traceable channel serial number. The interaction result for this round is fixed to represent the actual marketing interaction completed by the marketing staff member surrounding the target customer after this verification, and includes at least the main customer number, batch number, qualification result number, interaction initiation time, interaction end time, execution channel identifier, mandatory inherited content referenced in this round, mandatory avoided content removed in this round, prohibited duplicate inquiries removed in this round, pending matters actually promoted in this round, and interaction conclusion. The interaction conclusion for this round is fixed to be recorded as one of five categories: continued promotion, confirmation, customer rejection, no response, and channel closure. Confirmation means a new valid confirmation result has been formed in the interaction record for this round; customer rejection means an explicit rejection is stated in the interaction record for this round; and no response means the channel has accepted the interaction but... If no valid response is obtained from the customer within the current interaction confirmation window, the response waiting period for the proposed channel will be used in the current marketing task configuration record. If no separate response waiting period is written in the current marketing task configuration record, the preset response waiting period for the proposed channel will be used. This period will be calculated continuously from the time the interaction is initiated. If no valid response is obtained from the customer by the end of the window, it will be recorded as no response. Channel closure is defined as when a formal interaction record has been generated and the proposed channel has returned to a closed state or a state where interaction cannot continue. Continuing to proceed is defined as when an interaction has been initiated but the aforementioned four types of results have not been achieved. The execution channel identifier must be consistent with the proposed channel in the current qualification results. The interaction initiation time is the time when the channel was successfully initiated, and the interaction end time is the time when the channel returned to a completed state. If the channel initiation is unsuccessful and no formal interaction record is generated, no interaction result will be generated for this round, and the channel will be transferred to the supplementary recording area. The supplementary recording area must retain at least the main customer number, collection batch number, qualification result number, proposed channel, and reason for initiation failure.

[0067] Within the current batch, only one valid interaction result will be retained for the same primary customer number, the same collection batch number, and the same qualification result number. Records that were not written in the previous round will be overwritten, while those that were written in the previous round will not be duplicated and parallel records will not be added. The source version of the interaction result will be the qualification rule version number corresponding to the current qualification result and the acceptance interface version number corresponding to the acceptance constraint record. No new interaction rule version number will be generated.

[0068] After the results of this round of interaction are generated, they are written into the interaction result storage area in the order of main customer number, collection batch number, and qualification result number, and then submitted to the next stage with the main customer number, collection batch number, interaction result number, the conclusion of this round of interaction, and the pending matters actually promoted in this round.

[0069] S6. Extract newly confirmed items, stage change information, and channel status change information from the current round of interaction results and write them back to the continuous marketing conversation ledger. When the transition trigger condition is met, regenerate the acceptance constraint record and enter the next round of acceptance qualification verification. The specific implementation is as follows: After the results of this round of interactions are written to the interaction result storage area, the session write-back execution unit set up at the enterprise's marketing business site retrieves the corresponding interaction results of this round according to the main customer number, collection batch number, and interaction result number. Within the same target customer, the same marketing task scope, and the same preset marketing cycle, it sequentially extracts newly confirmed items, stage change information, and channel status change information, and writes them back to the continuous marketing session ledger. Among them, the interaction results of this round are always the valid interaction results that have been written in the previous stage and have not been replaced by the updated results under the same main customer number, the same collection batch number, and the same qualification result number. Draft results, invalid results, and results to be supplemented are not called.

[0070] When extracting newly confirmed items, first read the current round's interaction conclusion, the items to be promoted in this round, the required inherited content referenced in this round, and the channel interaction traces corresponding to the original record reference number from the current round's interaction results. Newly confirmed items are fixed as the item names that form a valid confirmation result for the first time in this round of interaction and were not included in the set of confirmed items before this round of interaction was initiated. Where the current round's interaction conclusion is not a confirmed result, no new confirmed items are extracted. If the current round's interaction conclusion is recorded as a confirmed result and there is a clear confirmation record in the channel interaction trace, the item corresponding to that confirmation record is used as the newly confirmed item. Confirmation records that are fixed refer to confirmation records in the channel interaction logs that have been written with the confirmation completion status value, confirmation item name, and confirmation completion time. If there is only unstructured agreement text and no confirmation status value is formed, it will not be counted as a new confirmation item. After each confirmation record is matched with the items to be promoted in this round, only the consistent items are retained. Inconsistent items are not counted as new confirmation items. Items that already exist as existing results in the mandatory inheritance content referenced in this round will not be counted again as new confirmation items. If the same item forms confirmation records multiple times in this round of interaction, only the last valid confirmation record corresponding to the time of the end of the interaction will be retained.

[0071] When extracting stage change information, first read the interaction conclusions, pending items, and newly confirmed items from the current interaction results. Then, compare each item with the stage division criteria that the current marketing task has taken effect and was locked at the start of this write-back. Stage change information consistently represents the change in the current marketing stage after this round of interaction execution relative to the current marketing stage before the write-back, and is consistently recorded using one of three results: stage advancement, stage maintenance, or stage rollback. Among them, newly confirmed items that enter the mandatory items of the current marketing stage and pending items of the current stage are no longer retained as mandatory items of the current stage after this round of interaction are recorded as stage advancement. The target stage after the advancement is fixed as the only stage immediately following the current marketing stage in the current marketing task stage division criteria; if the conclusion of this round of interaction is recorded as continue advancement, no response, customer rejection, or channel closure and the stage advancement conditions are not met, it is recorded as stage maintenance; if there is a clear rollback record and the rollback record has been written into the channel interaction record, manual processing record, or business confirmation record corresponding to the original interaction result reference number, it is recorded as stage rollback. The aforementioned clear rollback record is fixed as a valid record that has been written with a stage rollback identifier or has written a record of canceling the current stage confirmation result and restoring the previous stage state; if there is no clear rollback record, no stage rollback result is generated.

[0072] When extracting channel status change information, first read the execution channel identifier, the conclusion of this round of interaction, the interaction initiation time, the interaction end time, and the channel interaction trace from the current round of interaction results. The channel status change information permanently represents the change in the corresponding status of the execution channel after this round of interaction execution relative to the current channel status before write-back. The result status is selected from pending response, responded, ongoing communication, manual follow-up, closed, and channel closed, and recorded according to the criteria of maintaining or changing. Among them, if the conclusion of this round of interaction is recorded as no response received, the channel status change information is recorded as pending response and maintained; if the conclusion of this round of interaction is recorded as continuing and there is a valid customer response in the channel interaction trace, the channel status change information is recorded as ongoing communication. The aforementioned valid customer response is fixed to refer to the response status that has been formed in the channel interaction trace. Customer response records that are not blank, not automatically received by the system, and not duplicate failure receipts; if the conclusion of this round of interaction is marked as confirmation and the corresponding channel loop is completed, the channel status change information is marked as closed. The aforementioned confirmation corresponding to the completion of the current channel loop means that the confirmed item is marked as completed in the pending items of the current channel and the current channel no longer retains the pending item record; if the conclusion of this round of interaction is marked as channel closed, the channel status change information is marked as channel closed; if the conclusion of this round of interaction is marked as customer rejection but the channel can still continue to interact, the channel status change information is marked as responded and maintained. The aforementioned customer rejection is a valid feedback to this round of interaction. Since a valid response has been formed but a closed loop has not been formed, it is marked as responded and maintained.

[0073] After the aforementioned extraction is completed, the conversation write-back execution unit generates and appends the current cycle write-back ledger record to the continuous marketing conversation ledger in the order of "first new confirmed items, then stage change information, and finally channel status change information". This current cycle write-back ledger record refers to the ledger record formed by the new confirmed items, stage change information, and channel status change information extracted from the current interaction results and appended to the continuous marketing conversation ledger. This ledger record, after being written, serves as the source of a single ledger record for subsequent conversation segment extractions and participates in subsequent status extractions. This current cycle write-back ledger record must at least include the main customer number, collection batch number, interaction result number, record category, occurrence time, execution channel identifier, new confirmed items, stage change information, and channel status change information. The system includes information on segment changes, channel status changes, original interaction result reference numbers, and write-back rule version numbers. The record category is fixed as "interaction write-back record," and the occurrence time is fixed as the interaction end time. This ensures that newly added confirmed items, segment changes, and channel status changes are all recorded based on the final result after the completion of this round of interaction. The write-back rule version number is read and locked at the start of this write-back. Records already written in this round of write-back will not be overwritten due to subsequent rule adjustments. Only one valid record of this round of write-back is retained under the same primary customer number, the same collection batch number, and the same interaction result number. Records that were not written in the previous round are allowed to be overwritten, and records that were written in the previous round are not allowed to be added again as parallel records.

[0074] After the write-back is completed, the latest continuous marketing session ledger is reread according to the main customer number, collection batch number, and interaction result number. First, the corresponding current session status record is re-formed based on the latest continuous marketing session ledger. Then, it is written into the session status record storage area according to the main customer number, collection batch number, and the new read-end ledger record sequence number. Next, the transition trigger conditions written in the previous valid acceptance constraint record corresponding to this round of interaction results are used as the sole criterion for comparison. The aforementioned previous valid acceptance constraint record is fixed to the acceptance constraint record pointed to by the constraint record number corresponding to this round of interaction results and still in a valid state at the start of this round of write-back. The same main customer number, the same collection batch number, and the same interaction result number are all considered valid. Only one previous valid acceptance constraint record is taken under the batch number and the same interaction result number. When all the transition trigger conditions are met, after the newly formed current session status record is written, the acceptance constraint record is regenerated based on the current session status record. The transition trigger conditions are fixed to the core matter confirmation condition, the current channel status matching condition, and the current stage pending matter clearing condition that have been written in the previous valid acceptance constraint record. The transition trigger conditions are considered to be valid only when the above three conditions are met at the same time. If any condition is not met, the acceptance constraint record is not regenerated, nor does it enter the next round of acceptance qualification verification. Only the current valid acceptance constraint record remains effective.

[0075] After regenerating the acceptance constraint record, the session write-back execution unit writes it into the acceptance constraint record storage area according to the main customer number, collection batch number, and new constraint record number, and then proceeds to the next round of acceptance qualification verification after the writing is completed. The next round of acceptance qualification verification refers to submitting the main customer number, collection batch number, and new constraint record number to the acceptance qualification verification execution unit, which then re-performs the item-by-item verification of the subject attribute, channel attribute, and task attribute for the next marketing digital employee to be executed.

[0076] Preferably, in the e-commerce private domain activation scenario, when the result of this round of interaction is recorded as confirmed and the pending item actually promoted in this round is in-store appointment, the newly confirmed item can be extracted as in-store appointment, the stage change information is stage progress, the channel status change information is closed, and after all the transition trigger conditions are met, the acceptance constraint record is regenerated and the next round of acceptance qualification verification is entered.

[0077] In the operational scenario shown in this embodiment: taking the private domain in-store conversion marketing task of a chain dental clinic as an example, the enterprise pre-sets the main customer number, marketing task scope, preset marketing cycle, stage division criteria, item criteria table, channel status mapping table, acceptance interface criteria table, task configuration record and write-back rule version number corresponding to this marketing task in the marketing task configuration record, and connects the SMS delivery terminal, social message terminal, human agent handling page, and appointment confirmation page to the same marketing business system.

[0078] In this marketing campaign, a target customer has a fixed primary customer ID. Within the preset marketing period, the SMS outreach platform first generates a channel interaction record of "teeth cleaning discount reminder sent," followed by a channel interaction record of "customer reply inquiring about teeth cleaning package details" on social media. The human agent handling page generates a human processing record of "human supplementary explanation of applicable stores and usage conditions," and the appointment confirmation page generates a business confirmation record of "in-store appointment confirmed." When the batch collection is initiated, the conversation processing execution unit sequentially pulls the aforementioned channel interaction records, human processing records, and business confirmation records. It filters by primary customer ID, filters by preset marketing period, performs time conversion according to Beijing time second-level timestamp, and generates a continuous marketing conversation ledger after mixing and sorting by occurrence time. Among them, SMS outreach records, customer inquiry records, human explanation records, and appointment confirmation records form continuous ledger records in the ledger.

[0079] Subsequently, the conversation status processing unit extracts the status of each conversation segment based on the continuous marketing conversation ledger: for SMS discount reminders, the current marketing stage is extracted as initial contact; for customer inquiries about package content, the current marketing stage is updated to intention establishment or solution communication; for manual supplementary explanations of stores and conditions, the current receiving entity is a human agent and the current channel status is continuous communication; for appointment confirmations, "in-store appointment" is added to the confirmed items, and completed questions and answers such as "Do you have an intention to come to the store?" and "Have you confirmed the appointment time?" are included in the prohibited repeated questions and answers. "In-store verification" is retained as an item to be promoted, and finally the current conversation status record is formed.

[0080] After reading the current session state record, the constraint processing and execution unit generates a constraint record based on the current marketing stage, current channel status, current receiving entity, confirmed items, prohibited duplicate inquiries, and pending items. The receiving stage is allowed to retain appointment confirmations and adjacent subsequent stages; the receiving channel is allowed to retain the current social messaging platform and enable SMS notifications; the receiving entity is allowed to include human agents and marketing digital staff. The mandatory inherited content includes "Customer has inquired about package details," "Applicable stores and usage conditions have been explained," and "In-store appointment confirmed." The mandatory avoided content includes "Has the package details been inquired about?" and "Has the appointment time been confirmed?" Transition trigger conditions include "In-store appointment enters confirmed item," "Current channel status reaches the closed or completed closed-loop state," and "Pending items in the appointment confirmation stage are cleared."

[0081] Based on this, the qualification verification execution unit selects social messages from the queue to be executed and automatically reaches the subject. It then verifies the subject attributes, channel attributes, and task attributes against the acceptance constraint records item by item. Once the verification is passed, the current qualification result is generated, and the comprehensive qualification identifier is recorded as having the qualification to accept.

[0082] After reading the current acceptance qualification results and acceptance constraint records, the marketing interaction execution unit first writes "Customer has inquired about package details," "Applicable stores and usage conditions have been explained," and "In-store appointment has been confirmed" into the acceptance context. Then, it removes content that must be avoided, such as "Whether package details have been inquired about" and "Whether appointment time has been confirmed," as well as items that should not be asked repeatedly, from the items to be initiated in this round. Only "In-store verification reminder" and "Pre-store preparation tips" are retained as the actual items to be promoted in this round. This round of marketing interaction is initiated through the social messaging terminal, forming a formal interaction record of "In-store verification reminder has been sent, and the customer has replied to confirm that they are aware," and generating the interaction result of this round. The conclusion of this round of interaction can be recorded as "Continue to promote" or "Confirmation has been formed."

[0083] Subsequently, the conversation write-back execution unit extracts newly confirmed items, stage change information, and channel status change information from the results of this round of interaction. For example, it extracts "in-store verification confirmation" as a newly confirmed item, advances the current marketing stage from appointment confirmation to service follow-up, records channel status change information as closed or responded to and maintained, and appends the aforementioned content to the continuous marketing conversation ledger to form an interaction write-back record. After the write-back is completed, the current conversation status record is re-formed based on the latest continuous marketing conversation ledger, and each item is compared according to the transition trigger conditions in the previous valid acceptance constraint record. When the core items corresponding to the "appointment confirmation" stage have been confirmed, the current channel status meets the requirements of the acceptance interface table, and the items to be promoted in the appointment confirmation stage have been cleared, the transition trigger conditions are deemed to be met, a new acceptance constraint record is regenerated, and the new constraint record number is submitted to the acceptance qualification verification execution unit to enter the next round of acceptance qualification verification, thereby realizing the closed-loop operation of continuous marketing outreach, acceptance, interaction, write-back, and re-acceptance around the same target customer within the same marketing task scope.

[0084] The calculations involved in the embodiments are all dimensionless numerical calculations, and the preset parameters and thresholds in the calculations are set by those skilled in the art according to the actual situation.

[0085] It should be noted that this invention can be deployed on the device itself to realize embedded applications, or it can run on a PC or other terminal with a user interface, thereby meeting various hardware environments and usage requirements.

[0086] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wireless or wired transmission; wired transmission methods include optical fiber, twisted pair, coaxial cable, etc.; wireless transmission includes infrared, microwave, etc. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center containing one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0087] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and modules described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0088] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0089] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0090] In addition, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module.

[0091] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0092] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0093] In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A multi-agent collaborative marketing digital employee interaction method, characterized in that, include: S1. Collect channel interaction records, manual processing records, and business confirmation records of target customers within a preset marketing cycle, sort them according to a unified time base, and generate a continuous marketing conversation ledger. S2. Extract the current marketing stage, current channel status, current responsible entity, confirmed items, prohibited repeated inquiries, and pending items from each session segment in the continuous marketing session ledger to form a current session status record; S3. Based on the current session state record, extract the allowed acceptance stage, allowed acceptance channel, allowed acceptance subject, must-inherit content, must-avoid content, and transition trigger conditions to generate an acceptance constraint record; S4. Retrieve the subject attributes, channel attributes, and task attributes of the marketing digital employee to be executed, and verify them against the acceptance constraint record item by item to generate the current acceptance qualification result; S5. When the current qualification result is valid, marketing interactions are performed based on the mandatory inheritance content, mandatory avoidance content, prohibited repeated inquiry items, and pending items in the acceptance constraint record to generate the current round of interaction results. S6. Extract newly confirmed items, stage change information, and channel status change information from the current round of interaction results and write them back to the continuous marketing session ledger. When the transition trigger conditions are met, regenerate the acceptance constraint record and enter the next round of acceptance qualification verification.

2. The multi-agent collaborative marketing digital employee interaction method of claim 1, wherein, S1 includes: Filter channel interaction records, manual processing records, and business confirmation records by primary customer number; The selected records are filtered according to the preset marketing cycle; The filtered records are converted to a time based on a unified time standard; Perform lead and trailing space removal, space folding, line break folding, and separator folding on the interactive content records and processing item records; Complete the interaction end time in the channel interaction record; Remove duplicates from the converted records; A continuous marketing session ledger is generated by sorting channel interaction records, manual processing records, and business confirmation records according to the time of occurrence.

3. The multi-agent collaborative marketing digital employee interaction method of claim 1, wherein S2 include: Read the main items, record category, and original record citation number of each session segment in the continuous marketing session ledger according to the time of occurrence; Extract the current marketing stage, current channel status, current responsible entity, confirmed matters, matters that should not be repeatedly inquired about, and matters that need to be promoted; Generate the current session status record based on the primary customer number, the batch number, and the sequence number of the last ledger record read.

4. The multi-agent collaborative marketing digital employee interaction method according to claim 1, characterized in that, S3 includes: Retrieve the current session state record; Based on the current marketing stage, current channel status, current undertaking entity, confirmed matters, prohibited repeated inquiries, and pending matters, extract the allowed undertaking stage, allowed undertaking channel, allowed undertaking entity, mandatory inherited content, mandatory avoided content, and transition trigger conditions; Generate acceptance constraint records based on the main customer number, collection batch number, and status record number.

5. The multi-agent collaborative marketing digital employee interaction method according to claim 1, characterized in that, S4 include: Retrieve the acceptance constraint record; Retrieve the subject attributes, channel attributes, and task attributes of the marketing digital employees to be executed; The subject attributes, channel attributes, and task attributes are checked item by item along with the acceptance constraint records in the order of subject attributes, channel attributes, and task attributes. Generate the current qualification results based on the main customer number, collection batch number, constraint record number, and pending marketing digital employee identifier.

6. The multi-agent collaborative marketing digital employee interaction method according to claim 5, characterized in that, The current eligibility results include: Result of verification of main attributes, result of verification of channel attributes, result of verification of task attributes, comprehensive undertaking qualification identifier, time of qualification formation, and version number of qualification rules; When the verification results of the main body attribute, channel attribute, and task attribute are all passed, the comprehensive qualification mark indicates that the contractor is qualified to undertake the project. In other generated result scenarios, the comprehensive qualification identifier will be marked as not having the qualification to undertake the task.

7. A multi-agent collaborative marketing digital employee interaction method according to claim 1, characterized in that, S5 include: Retrieve the current eligibility results and acceptance constraint records; When the comprehensive qualification mark indicates that the contractor is qualified, the interactive content of this round is formed in the following order: first inheritance, then avoidance, then removal of duplicate inquiries, and finally retention of items to be promoted. The content to be inherited, the content to be avoided, the items to be repeatedly inquired about, and the items to be promoted are all in order. The marketing digital staff to be executed initiates this round of marketing interaction through the channels to be used, and the result of this round of interaction is formed by the formal interaction record.

8. A multi-agent collaborative marketing digital employee interaction method according to claim 1, characterized in that, S6 include: Retrieve the interaction results of this round by main customer number, collection batch number, and interaction result number; Extract newly confirmed items, stage change information, and channel status change information; The cost cycle is recorded in the ledger and appended to the continuous marketing conversation ledger, following the order of newly confirmed items, stage change information, and channel status change information. Using the transition trigger conditions already written in the previous valid acceptance constraint record as the basis for judgment, when the transition trigger conditions are met, the acceptance constraint record is regenerated based on the newly formed current session state record, and the new constraint record number is submitted to the acceptance qualification verification execution unit.

Images